Fix generated PR author policy - #1234
Draft
danielporterda wants to merge 1 commit into
Draft
Conversation
Signed-off-by: danielporterda <daniel.porter@digitalasset.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
app/cf-docs-generated-docs-mergerapp/github-actionsidentityRoot cause
PR #1201 moved generated PR mutations from
GITHUB_TOKENto the merger GitHub App, but the auto-merge safety validator continued to requireapp/github-actions. Scheduled run https://github.com/canton-network/cf-docs/actions/runs/31019375817 therefore created valid App-authored PRs #1230 and #1231 and then rejected them before auto-merge.Validation
42 passedintests/test_update_generated_reference_prs.py6 passed, 36 deselectedfor generated-PR policy and merge-path testsgit diff --check3694303700399e3ee81a4e16ef276216c87ff51f64e5d08d2d9736237314a30b9bb8cae2acfe6738Local
.envrcsetup was attempted first; this machine does not providenix-shell, so focused tests ran in an isolated Python environment from.[dev].