Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport action #8191

Merged
merged 5 commits into from
May 31, 2024
Merged

Backport action #8191

merged 5 commits into from
May 31, 2024

Commits on Apr 17, 2024

  1. Add workflow for backporting pull requests

    Fixes #8181
    
    This commit includes the configuration file for an action that:
    
    * When a PR that has a label like "Backport <branch>" is merged,
      it will trigger a backport action
    * If the PR commits merge cleanly into the target branch, a new PR will
      be created against it, assigned to the same user as the merged one.
      The usual checks will be run on the new PR
    * If the commits don't merge cleanly, a comment will be posted on the
      orginal PR with the manual commands to fix the conflicts, and the PR
      will be labelled with "Backport failed"
    * Additionally, Tech Team members can trigger a backport on open or
      already closed PRs adding a comment starting with `/backport` (and
      adding the relevant label)
    
    Some more details:
    * The action is run using a token from the @ckanbot account, this needs
      to be stored in the repository secrets (`BACKPORT_ACTION_PAT`)
    * There are also two public variables (`TECH_TEAM_USER_IDS` and
      `CKANBOT_USER_ID`) that need to be added to the repository variables.
    * The action used source code code can be found at
      https://github.com/korthout/backport-action
    amercader committed Apr 17, 2024
    Configuration menu
    Copy the full SHA
    31d87e7 View commit details
    Browse the repository at this point in the history

Commits on Apr 18, 2024

  1. Configuration menu
    Copy the full SHA
    b7ca756 View commit details
    Browse the repository at this point in the history
  2. Fix doc build issue

    amercader committed Apr 18, 2024
    Configuration menu
    Copy the full SHA
    d0e8bab View commit details
    Browse the repository at this point in the history
  3. Add changelog

    amercader committed Apr 18, 2024
    Configuration menu
    Copy the full SHA
    0d035e9 View commit details
    Browse the repository at this point in the history
  4. Fix docs again

    amercader committed Apr 18, 2024
    Configuration menu
    Copy the full SHA
    cb26a6c View commit details
    Browse the repository at this point in the history