Adding documentation for maven publishing automation #646
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
Rijai/mavenworkflow
Merging main to mavenworkflow branch
jainr
changed the title
jainr
requested review from
blee1234,
blrchen,
edwincheung,
xiaoyongzhu and
Yuqing-cat
blee1234
approved these changes
Sep 6, 2022
edwincheung
approved these changes
Sep 6, 2022
xiaoyongzhu
approved these changes
Sep 7, 2022
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.
Description
This PR is a follow up for the previous PR adding automation for maven publishing. This PR adds the documentation capturing steps and gotchas in creating such pipeline.
Alongwith a minor fix in the workflow file itself.
How was this PR tested?
No test required, it's a documentation PR.
Does this PR introduce any user-facing changes?