-
-
Notifications
You must be signed in to change notification settings - Fork 596
change issue templates according to change in parse server #1207
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
change issue templates according to change in parse server #1207
Conversation
@TomWFox How did you add the "Report a vulnerability" item in the issue list in parse server? I couldn't see anything in the |
Report a vulnerability is there by default if you have a SECURITY.md file |
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.
Looks good to me!
Although not sure about adding a SECURITY.md file, it does pull in the one from the .github repo (and add the link in the issue type chooser). From an admin perspective it's easier to keep repos pointed to the central one - I made like 20+ PRs to change the email address in the code of conduct doc. |
I'll wait for @dplewis as a frequent wanderer of the JS SDK issue list to get his approval. |
Absolutely, my bad, we talk about deduplication in the docs and here I duplicate 🤦♂️ I'll point to the existing file and remove this one. Edit: but how would I point to the existing file? |
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.
Frequent wanderer
I like that
Github magic will do that for you - if you look at the current issue list report a vulnerability is already an option - I think the only prerequisite is to have more than one issue template (so that the issue list shows up when you click new issue) |
This reverts commit 401bbff.
Alright, removed the securities file, I think this is ready for review. |
issue templates changed according to recent changes in parse server:
changed specifically here: