Feature/publishing packages doc page #1211
Open
Conversation
This file contains hidden or 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
Signed-off-by: Bryce Gattis <[email protected]>
Signed-off-by: Bryce Gattis <[email protected]>
Signed-off-by: Bryce Gattis <[email protected]>
|
just noting that we do have this tiny section, which should either link or is potentially a place to put additional detail: https://spkenv.dev/use/#publish-a-package |
|
just realizing that this is a merge request not an issue (thanks!) so maybe a link from that area mentioned above would be prudent |
Signed-off-by: Bryce Gattis <[email protected]>
|
Done. Just need more info on any additional processes that run when running |
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 new publishing packages doc page since we didn't seem to have anything that explained what "publishing" a package meant and how to configure it.
Would be awesome if we could break out our configuration settings individually and could link to them like this. That way this doc page could just link to these hyperlinks rather than duplicate the config info.
TODO:
spk publishdoes at the bottom of this new doc page.