(Originally #20, but I am opening a new one with a more-updated scope and proposal)
Concern: When merging into a branch, a target version label should be added to the PR. This is important for generating release notes, and, in general, knowing which PRs are impacting a given version of a product.
Proposal: Ask the target branch what product version it is and use that version to add a label to the PR.
Dependency: Requires we have a programmatic way to determine the product version given a branch. Today, I think most of our projects have different mechanisms for defining the version in the source tree.
Example proposed behavior: merge https://.../some/pull master 6.x 6.0 5.6
The above should inspect each branch for the version of that branch and the result should be the following labels (at time of writing):
6.x branch is "6.1.0"
6.0 branch is "6.0.0-rc1"
master branch is "7.0.0-alpha1"
So the result is that on the given pull, the following labels would be added: v6.1.0, 6.0.0-rc1, 7.0.0-alpha1
(Originally #20, but I am opening a new one with a more-updated scope and proposal)
Concern: When merging into a branch, a target version label should be added to the PR. This is important for generating release notes, and, in general, knowing which PRs are impacting a given version of a product.
Proposal: Ask the target branch what product version it is and use that version to add a label to the PR.
Dependency: Requires we have a programmatic way to determine the product version given a branch. Today, I think most of our projects have different mechanisms for defining the version in the source tree.
Example proposed behavior:
merge https://.../some/pull master 6.x 6.0 5.6The above should inspect each branch for the version of that branch and the result should be the following labels (at time of writing):
So the result is that on the given pull, the following labels would be added:
v6.1.0,6.0.0-rc1,7.0.0-alpha1