-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add Snap allowlist process issue templates #83
Conversation
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.
We have been tasked with documenting our process for allowlisting Snaps and I think it is best to use the issues in the repository itself. Will start using this right away.
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.
Some nits, some suggestions.
Co-authored-by: Maarten Zuidhoorn <[email protected]>
Co-authored-by: Maarten Zuidhoorn <[email protected]>
Co-authored-by: Maarten Zuidhoorn <[email protected]>
Co-authored-by: Maarten Zuidhoorn <[email protected]>
Co-authored-by: Maarten Zuidhoorn <[email protected]>
Co-authored-by: Maarten Zuidhoorn <[email protected]>
.github/ISSUE_TEMPLATE/block-snap.md
Outdated
|
||
Note: Blocking a Snap means that both new and existing users cannot use the Snap. | ||
|
||
All items in the list below needs to be satisfied. |
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 would move this below the "Checklist" header, but this is ok too.
No description provided.