Repository navigation
Backbot: Post one summary comment and include original PR description in backports - #11164
Conversation
yhabteab
added
the
backport-to-support/2.16
Set `comment_style: summary` so the action leaves one comment that links all backport PRs, instead of one comment per target branch.
Add `${pull_description}` to the backport PR body so reviewers see
the original context without having to open the source PR.
`sha` isn't a valid `actions/checkout` input (it's `ref`), so the attempt to pin the PR head commit was silently ignored and the job has always checked out the base branch. That's also the right thing to do: the backport action fetches the PR commits and cherry-picks them onto the support branches itself, so it doesn't need the PR head checked out.
yhabteab
added
github_actions
|
Backport-action found no target branches to backport this pull request to in workflow run 42643771284. This can happen when the pull request has no labels matching To avoid unnecessary action runs, update your workflow so this action only runs for PRs that should be backported, such as PRs with a matching backport label or runs with explicit |
|
Was this some kind of race condition between you removing the backport label and merging this PR? 🤨 Otherwise I don't know how this change is supposed to cause that. |
|
I think, it's a new feature of that action :). I'll look if we can disable that somehow. |
|
It's due to |
Set
comment_style: summaryso the action leaves one comment that links all backport PRs, instead of one comment per target branch as used to. Lastly, add${pull_description}to the backport PR body to include the original PR, which will be relevant for Icinga/icinga-notifications#606.Also, dropped the ineffective
shainput from the checkout step for that action.