Closed github-actions[bot] closed 4 months ago
TODO: Why can't this trigger a CI build?
Found in https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target
To ensure repository security, branches with names that match certain patterns (such as those which look similar to SHAs) may not trigger workflows with the
pull_request_target
event.
Also found https://github.com/marketplace/actions/add-commit#the-commit-from-the-action-is-not-triggering-ci (by https://www.reddit.com/r/github/comments/x0h8v5/comment/imrczmr/)
Updated branch protection rule to make sure the build CI passes before we can merge.
@philippedistributive For PRs created by https://github.com/Distributive-Network/PythonMonkey/commit/a7b92e896ff6b077f161b9ae79a9f5e55f4434b5 like this, it should be good to merge as long as the build CI (https://github.com/Distributive-Network/PythonMonkey/blob/main/.github/workflows/test-and-publish.yaml, not the CodeQL ones) passes.
Changeset: https://hg.mozilla.org/mozilla-central/rev/bc4609b7aa7a3dff961f43d527bc66c5c85f6f4b