-
Notifications
You must be signed in to change notification settings - Fork 3
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
feature: add link issues check #74
Conversation
src/utils/getConnectedIssueForPR.js
Outdated
* which is an error that cannot be suppressed | ||
**/ | ||
/* eslint-disable-next-line */ | ||
'^(.* )?link: (?<owner>openstax)\/(?<repo>[a-z\-]+)#(?<number>[0-9]+)( .*)?$', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the text link:
necessary? If it is to differentiate from someone saying something like This is a followup to #123
then maybe additional phrases should be included. Examples
refs #123
fixes openstax/foo#123
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea i agree that the word "link" could be better. maybe just for: openstax/foo#123
would be clearer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the README with a description of this feature
This verifies that the Pull Request description contains a link to the Issue that it fixes.