Updated Snap guidelines to include Snaps where the binary is built from source #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nary is built from source
…nary is built from source undid some automatic markdown formatting
jdkandersson
previously approved these changes
Mar 11, 2024
yanksyoon
previously approved these changes
Mar 11, 2024
cbartz
previously approved these changes
Mar 11, 2024
codethulu
dismissed stale reviews from cbartz, yanksyoon, and jdkandersson
via
92dad53
arturo-seijas
approved these changes
Mar 14, 2024
merkata
approved these changes
Mar 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While working on ISD-1600, we notice that the current charm contributing guide is too restrictive with respect to what Snaps should be used. We aim to resolve this by opening up the accepted Snaps we use internally to include those that are built from source and trusted.