mirror of
https://github.com/CHN-beta/nixpkgs.git
synced 2026-01-11 18:32:23 +08:00
We intend to use the edited event to react to base branch changes - but
before this change, we also ran those jobs on simple edits like title or
description.
While this works for some of the quicker jobs, it will not be
sustainable for all evaluation-related jobs. But evaluation needs to be
re-triggered on a base branch change as well, thus this change.
(cherry picked from commit 9b01e09a35)
50 lines
2.2 KiB
YAML
50 lines
2.2 KiB
YAML
# Some workflows depend on the base branch of the PR, but changing the base branch is not included in the default trigger events, which would be `opened`, `synchronize` or `reopened`.
|
|
# Instead it causes an `edited` event.
|
|
# Since `edited` is also triggered when PR title/body is changed, we use this wrapper workflow, to run the other workflows conditionally only.
|
|
# There are already feature requests for adding a `base_changed` event:
|
|
# - https://github.com/orgs/community/discussions/35058
|
|
# - https://github.com/orgs/community/discussions/64119
|
|
#
|
|
# Instead of adding this to each workflow's pull_request_target event, we trigger this in a separate workflow.
|
|
# This has the advantage, that we can actually skip running those jobs for simple edits like changing the title or description.
|
|
# The actual trigger happens by closing and re-opening the pull request, which triggers the default pull_request_target events.
|
|
# This is much simpler and reliable than other approaches.
|
|
|
|
name: "Edited base branch"
|
|
|
|
on:
|
|
pull_request_target:
|
|
types: [edited]
|
|
|
|
permissions: {}
|
|
|
|
jobs:
|
|
base:
|
|
name: Trigger jobs
|
|
runs-on: ubuntu-24.04
|
|
if: github.event.changes.base.ref.from && github.event.changes.base.ref.from != github.event.pull_request.base.ref
|
|
steps:
|
|
# Use a GitHub App to create the PR so that CI gets triggered
|
|
# The App is scoped to Repository > Contents and Pull Requests: write for Nixpkgs
|
|
# We only need Pull Requests: write here, but the app is also used for backports.
|
|
- uses: actions/create-github-app-token@df432ceedc7162793a195dd1713ff69aefc7379e # v2.0.6
|
|
id: app-token
|
|
with:
|
|
app-id: ${{ vars.NIXPKGS_CI_APP_ID }}
|
|
private-key: ${{ secrets.NIXPKGS_CI_APP_PRIVATE_KEY }}
|
|
permission-pull-requests: write
|
|
|
|
- env:
|
|
GH_TOKEN: ${{ steps.app-token.outputs.token }}
|
|
REPOSITORY: ${{ github.repository }}
|
|
NUMBER: ${{ github.event.number }}
|
|
run: |
|
|
gh api \
|
|
--method PATCH \
|
|
/repos/"$REPOSITORY"/pulls/"$NUMBER" \
|
|
-f "state=closed"
|
|
gh api \
|
|
--method PATCH \
|
|
/repos/"$REPOSITORY"/pulls/"$NUMBER" \
|
|
-f "state=open"
|