Mention how to discover existing sbt keys #1107
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
The introduction to build definition goes in detail about what keys are and how to create them, but there's no information about what the list of keys are, and the user is left to pick up from the code samples that `name` or `organization` seem to exist. I suggest to add this short set of paragraph to let the user know how they can discover the current settings and tasks.
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.
This introduction to build definition goes in detail about what keys are and how to create them, but there's no information about what the list of keys are, and the user is left to pick up from the code samples that
nameororganizationseem to exist.I suggest to add this short set of paragraph to let the user know how they can discover the current settings and tasks.