-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat: add github issues link to regex #385
Conversation
Side note: when I opened the PR felt that's really similar to open sauced, then noticed you are one of the contributors there :) |
Yeah, great project 🤩 |
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.
Since you didn't change anything in main.ts or related files, I'm not surprised dist/*.js didn't change. Still, remember to run npm run all
locally before pushing.
Thank you for the suggestions! Just solved it and all tests passed 👍 |
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.
actually really surprised that anything in dist would be affected. perhaps there's a different node version or something. I'll probably just merge this and make sure things are cleaned up on the next release.
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.
Thanks again for the PR @a0m0rajab!
Thank you for accepting it! |
What type of PR is this? (check all applicable)
Description
This PR add the extra regex to detect the issues link in the body.
Related Tickets & Documents
Closes #384
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?