Hello maintainers. @motemen @onk
If possible, I hope this gem would have a feature that determines labels to be added to a created pull request by aggregating labels on merged pull requests.
Feature
Let's say we have 3 merged pull requests as follows.
- a pull request with a label:
["enhancement"]
- a pull request with labels:
["bug", "security"]
- a pull request without any label:
[]
Then, a pull request that git-release-pr creates would have labels: ["enhancement", "bug", "security"].
Implementation design
- Add
pr-release.aggregate_labels config.
- It accepts boolean-ish value:
"true" or "false"
- The default is
"false"
- If it is
"true", git-release-pr aggregates labels from merged pull requests.
- What if
pr-release.labels is given at the same time?
- Merge aggregated labels and
pr-release.labels setting.
pr-release.labels=foo,bar and aggregated labels are baz, then labels would be ["foo", "bar", "baz"].
If it's acceptable for this gem, I'm willing to make a pull request for this feature.
Hello maintainers. @motemen @onk
If possible, I hope this gem would have a feature that determines labels to be added to a created pull request by aggregating labels on merged pull requests.
Feature
Let's say we have 3 merged pull requests as follows.
["enhancement"]["bug", "security"][]Then, a pull request that
git-release-prcreates would have labels:["enhancement", "bug", "security"].Implementation design
pr-release.aggregate_labelsconfig."true"or"false""false""true",git-release-praggregates labels from merged pull requests.pr-release.labelsis given at the same time?pr-release.labelssetting.pr-release.labels=foo,barand aggregated labels arebaz, then labels would be["foo", "bar", "baz"].If it's acceptable for this gem, I'm willing to make a pull request for this feature.