Rewrite CONTRIBUTING.md to use the Github issue tracker instead of JIRA by elharo · Pull Request #898 · apache/maven-enforcer (original) (raw)
We likely need to do this across all the repos that have migrated to github issues.
| considered to be in Apache Maven Enforcer's scope. |
|---|
| + Submit a ticket for your issue, assuming one does not already exist. |
| + Clearly describe the issue including steps to reproduce when it is a bug. |
| + Open a Github issue for the issue, assuming one does not already exist. |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
| considered to be in Apache Maven Enforcer's scope. |
|---|
| + Submit a ticket for your issue, assuming one does not already exist. |
| + Clearly describe the issue including steps to reproduce when it is a bug. |
| + Open a GitHub issue for the issue, assuming one does not already exist. |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All this PR does is change the existing instructions from Jira to Github. The requirement to open an issue already existed in this document.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok so another change would be to remove it as we do not require this anymore now
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})