Document how to get bucket indexed #15
Merged
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
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.
Add a step to the "How do I use this template" list that allows the bucket to be indexed at https://scoop.sh search: Add the
scoop-buckettopic to your bucket's repository.(As a maintainer of my own bucket generated from this template, for a while, I was confused after I was getting indexed, and then it somehow stopped. Then I stumbled upon the
scoop-bucket-topic method in the reference below. I'm not sure what happened.)Opting-in to indexing seems like a common enough goal. Therefore, we should document it.
Topics are not inherited from templates, so this is a step that must be done manually.
Reference: https://github.com/ScoopInstaller/Scoop/wiki/Buckets#after-the-bucket-is-created