-
Notifications
You must be signed in to change notification settings - Fork 255
Ability to add labels/comments to linked issues/PRs #975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@agkphysics, I agree it is a very nice feature that I have been doing manually for this project because of how nice it is. It is an eventual goal but we have some minor stuff to solve first |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
still valuable, no effort towards implementation has been made yet. |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
Setting some ground work for this feature by enabling commit parsers to extract the issue numbers and PR numbers from commit messages. |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
Under initial development and design, will require a lot more API definitions for a set of issue tracking systems. Significant amount of work to be done. |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
Still in backlog |
It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue? |
Description
The NodeJS implementation of semantic-release has the ability to automatically tag relevant PRs and issues with specified labels with the
@semantic-release/github
plugin. It would be useful for this Python version to also be able to do so.Use cases
You can then easily see which issues and PRs have been released, and on which versions. Technically this is already possible for PRs by looking at the tags associated with the merge commit, but that requires extra steps.
Possible implementation
Since there is planned functionality for linking PRs into changelogs, presumably said PRs could be passed to a step that adds labels to them, or adds a comment on them.
Issues may be slightly more difficult as they are linked via PRs.
The text was updated successfully, but these errors were encountered: