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
Having some sort of meaningful indication on a PR that it is a backport is helpful, but it doesn't necessarily need to be the word "backport" in the title. The convention of putting the target backport branch as a prefix on the backport PR title would still be recognized by people using this tool frequently, and the backport label could be the thing that says the word "backport" in case people want that.
Using the branch prefix really helps with auditing PRs to ensure that they were properly backported since you'd have all of the necessary information you need about the PRs right in the linkbacks in the original PR.
For example, these linked backport PRs would be much more useful if they instead began with their target branch:
The text was updated successfully, but these errors were encountered:
Having some sort of meaningful indication on a PR that it is a backport is helpful, but it doesn't necessarily need to be the word "backport" in the title. The convention of putting the target backport branch as a prefix on the backport PR title would still be recognized by people using this tool frequently, and the backport label could be the thing that says the word "backport" in case people want that.
Using the branch prefix really helps with auditing PRs to ensure that they were properly backported since you'd have all of the necessary information you need about the PRs right in the linkbacks in the original PR.
For example, these linked backport PRs would be much more useful if they instead began with their target branch:
The text was updated successfully, but these errors were encountered: