doc: include org instructions in scoped publish #4772
Merged
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.
If you've not created an organization but try to publish to a scope, you'll get a "helpful" message telling you to publish the module... that you're trying to publish. Upon reading the documentation, there's no indication that you need to actually create an organization prior to trying to publish, making it... annoying to try to publish to a net new scope.
This PR adds some documentation telling people to create an org first. There's probably more context that could be added, but wanted to get this up while it's top of mind for me so I don't continue hitting this wall without doing anything to help alleviate it.
References