Repository navigation
ci: restore automatic Flutter update checks and merging - #33
Merged
Merged
Conversation
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.
Flutter update PRs created with GITHUB_TOKEN require manual workflow approval, while the separately dispatched CI run does not satisfy the PR's required checks. Use the FLUTTER_UPDATE_TOKEN repository secret to create updates and enable GitHub auto-merge, so the normal PR checks run and all required checks must pass before merging.
Remove the separate CI dispatch and workflow_run merge callback. Before enabling auto-merge, verify that the PR has the expected author, repository, branches, generated head commit, and only a modification to .github/flutter-version. Git commit authorship remains github-actions[bot].
Validation: local JavaScript/Bash syntax checks, 14 PR eligibility cases, 3 token validation cases, and git diff --check passed. All three required checks passed in https://github.com/hgraceb/nested_scroll_views/actions/runs/43863094466 and GitHub auto-merged this PR. Post-merge CI https://github.com/hgraceb/nested_scroll_views/actions/runs/43863771463 and updater dispatch https://github.com/hgraceb/nested_scroll_views/actions/runs/43863824998 both succeeded. The configured repository secret authenticated successfully. The repository already tests the latest stable (3.50.0), so the updater correctly created no update PR; the next version update will exercise the PAT-based PR creation and auto-merge path.