Skip to content

Conversation

@artembilan
Copy link
Collaborator

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.
@artembilan artembilan added this to the 0.0.1 milestone Jun 12, 2025
@artembilan artembilan added the enhancement New feature or request label Jun 12, 2025
@artembilan artembilan merged commit 7bdf65d into spring-io:main Jun 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

1 participant