Propagate changes from main into development - #1261
Closed
Wikid82 wants to merge 7 commits into
Closed
Conversation
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Jeremy <jhatfield82@gmail.com>
The repo's default branch is development, but release-please-action defaults its target-branch input to the repository default branch via the API regardless of which branch the push trigger fired on. Since release-please-config.json/.release-please-manifest.json only exist on main (by design), the action was looking for them on development and failing with "Missing required manifest config."
Lets a human manually re-fire branch propagation (main -> development) when the workflow_run trigger doesn't fire on its own, without needing to re-run the upstream Docker Build workflow. The job's `if:` condition is extended to admit workflow_dispatch runs, since github.event.workflow_run is unset in that context.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Contributor
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
Owner
Author
|
Superseded by a new PR carrying the resolved merge — GitHub PRs can't have their head branch repointed, and the head here ( |
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
2 participants
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.
Automated PR to propagate changes from main into development.
Manually opened because
propagate-changes.yml's sensitive-path gate blocked auto-creation — 4 files under.github/skills/differ between the branches (README.md, utility-bump-beta.SKILL.md, utility-version-check-scripts/run.sh, utility-version-check.SKILL.md), and.github/skills/is in.github/propagate-config.yml's sensitive_paths list. The gate is all-or-nothing across the whole diff, so those 4 files blocked the otherwise-safe workflow/CI changes from auto-propagating too.Please review the
.github/skills/diff specifically before merging.