Update docs to clarify workflow branch for release package publishing. #56183
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
tellthemachines
added
the
[Type] Developer Documentation
tellthemachines
requested review from
SiobhyB,
gziolo,
karmatosed and
mikachan
tellthemachines
requested review from
ajitbohra,
fabiankaegy,
juanmaguitar,
ndiego and
ryanwelcher
as code owners
gziolo
approved these changes
Nov 16, 2023
Member
gziolo
left a comment
gziolo
left a comment
There was a problem hiding this comment.
Thank you for including this clarification 😀
Member
|
Thank you for handling this! |
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.
What?
There has been confusion around which branch to run the package publishing workflow from for a while. This PR attempts to clarify in the docs that the workflow should usually be run from
trunk.