Skip to content
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

Add Fixes|Closes matching for issue link, too #21

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

artembilan
Copy link

The short syntax like Fixes: #123 is nice,
but we lose a link to the target issue when we deal with commit history outside the GitHub.
For example, I use commits UI in the IntelliJ IDEA and would like to jump to the issue by clicking link from the commit message. Adding an issue link into a Fixes|Closes pattern would let me avoid adding extra link into commit message and this bot would still do its job.

Also add a junit-vintage-engine dependency to be able to run JUnit 4 test from Gradle

The short syntax like `Fixes: #123` is nice,
but we lose a link to the target issue when we deal with commit history
outside the GitHub.
For example, I use commits UI in the IntelliJ IDEA and would like
to jump to the issue by clicking link from the commit message.
Adding an issue link into a `Fixes|Closes` pattern would let me avoid
adding extra link into commit message and this bot would still do its job.

Also add a `junit-vintage-engine` dependency to be able to run JUnit 4 test
from Gradle
* Fix `or` grouping in the pattern

Sometimes I don't have an issue but directly PR.
However, I still would like to have back-port issue to be created.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant