-
-
Notifications
You must be signed in to change notification settings - Fork 301
have a built-in option to create/check existing github issue #294
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
Comments
I really like the idea of giving extra feedback to package authors. Automatically creating issues could potentially be quite spammy tho 🤔. Also it would rely on the user having GitHub creds in their env. How about an opt-in thing like
And running that command would open a browser tab with the issue body pre-filled? Then we could let the users worry about auth, and it would be less likely to result in spam. |
Better than nothing. Only problem is most people will never use the flag. It will still be worth to add this as it could persuade people to create GH issues even for things they might be too lazy to report. |
I really appreciate your offer to prototype this 🙌 Your idea made me too excited to wait though 😅 and I pushed up a PR here #295 — let me know if there's anything you think could be improved! Thanks again for the suggestion. |
No probs, thanks for the speedy implementation. It looks good. I will give this a whirl the next time I am using patch-package for sure! |
This was released in 6.4.0 🎉 |
As a package author I would love to see when people feel the need to use this tool on my packages.
Ideally just a simple github API call that would create a github issue when a new patch is created.
The link to an issue could be reported in the output, so it would print out
When run again with the same patch it would output
Obviously you could skip this with a flag like
--noGithubReport
or something like this.Would this be an acceptable functionality @ds300 ?
The text was updated successfully, but these errors were encountered: