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
github: Use new issue template feature #5936
Conversation
This helps us to avoid getting feature requests as well as security bugs reported into the issue tracker. Closes curl#5936
0409e55
to
c95adc2
Compare
Instead of providing templates with these warnings it is also possible to directly link to the corresponding pages, eg.: |
Thanks, TIL |
This helps us to avoid getting feature requests as well as security bugs reported into the issue tracker. Closes curl#5936
c95adc2
to
c88584c
Compare
Fixed. Now security redirects to hackerone and feature request to the ML. |
I think it's fine to leave the comments in the bug_report.md file though |
For the case someone wants to test it: https://github.com/emilengler/curl-issue-test/issues/new/choose |
This helps us to avoid getting feature requests as well as security bugs reported into the issue tracker. Closes curl#5936
c88584c
to
4a739bc
Compare
@mback2k Adjustments applied |
That test link isn't showing the latest update, does it? |
Nope but it's only a text change. I can't update it from here unfortunately. I am on the ride |
Because it still says "ML" and not "mailing list".
Proposal: Report a bug, mistake or problem you've found in curl or libcurl, as detailed as possible.
Proposal: To propose new features or enhancements, please bring that discussion to a suitable curl mailing list.
Proposal: Please report security problems or just suspected security problems to the curl-security team, to allow us to assess and work on it privately before we release a fix and inform the public. |
Fourth entry "Question" and instruct that questions should be taken to a dedicated mailing list. A possible fifth entry could be "Commercial support" and saying that if the user is interested in hiring/paying someone for support, we provide alternatives on https://curl.haxx.se/support.html |
This helps us to avoid getting feature requests as well as security bugs reported into the issue tracker. Closes curl#5936
4a739bc
to
4b0cf6d
Compare
I implemented @bagder's proposals |
Awesome, can you refresh your example URL so that we can see how this looks "live" ? |
Yes I will do this in the afternoon! |
@bagder Updated |
This helps us to avoid getting feature requests as well as security bugs reported into the issue tracker. Closes curl#5936
4b0cf6d
to
5942062
Compare
I think this is ready for merge now, the demo is also updated |
url: https://curl.haxx.se/mail/ | ||
about: To propose new features or enhancements, please bring that discussion to a suitable curl mailing list. | ||
- name: Security vulnerability | ||
url: https://hackerone.com/curl |
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.
Would it make sense to link to https://curl.haxx.se/dev/secprocess.html instead?
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 don't think so. The secprocess page is more about describing how we approach it, if someone wants to report an issue I figured the hackerone page is more direct.
There's some talk earlier about a demo, how do I access that? |
Thanks! |
This helps us to avoid getting feature requests as well as security
bugs reported into the issue tracker.