You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The label function by default gets the labels from the most recently merged PR on any branch, not the most recently merged PR on the target branch. This can cause a potential race condition messing up releases.
For example:
PR A is merged into master, awaiting a release to be generated.
PR B is merged into next immediately after, with a skip-release label.
When auto is run for PR A, it picks up the skip-release label from PR B, thus not end up creating a release.
This issue will happen for any project with multiple release tracks.
To Reproduce
Repeat the above steps, and observe that the release labels for PR B will be used for the release of PR A.
Expected behavior
When auto is run on a specific branch to create releases, it should only pick up PRs merged from that branch, and not any other branches.
The text was updated successfully, but these errors were encountered:
Describe the bug
The
label
function by default gets the labels from the most recently merged PR on any branch, not the most recently merged PR on the target branch. This can cause a potential race condition messing up releases.For example:
master
, awaiting a release to be generated.next
immediately after, with askip-release
label.auto
is run for PR A, it picks up theskip-release
label from PR B, thus not end up creating a release.This issue will happen for any project with multiple release tracks.
To Reproduce
Repeat the above steps, and observe that the release labels for PR B will be used for the release of PR A.
Expected behavior
When
auto
is run on a specific branch to create releases, it should only pick up PRs merged from that branch, and not any other branches.The text was updated successfully, but these errors were encountered: