chore: now docs are autogenerated as part of the release process #157
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
nickytonline
force-pushed
the
nickytonline/automate-doc-updates
branch
2 times, most recently
from
8f1bb51 to
505573d
Compare
nickytonline
commented
Sep 6, 2024
nickytonline
commented
Sep 6, 2024
nickytonline
force-pushed
the
nickytonline/automate-doc-updates
branch
from
9e20c1e to
505573d
Compare
nickytonline
commented
Sep 6, 2024
nickytonline
commented
Sep 6, 2024
jpmcb
reviewed
Sep 6, 2024
nickytonline
force-pushed
the
nickytonline/automate-doc-updates
branch
from
505573d to
ae7bea3
Compare
jpmcb
approved these changes
Sep 9, 2024
brandonroberts
approved these changes
Sep 9, 2024
4 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.
Description
This pull request introduces a new job to the release workflow for automating the documentation update process before releasing a new version. Additionally, it ensures that the release process waits for the documentation update PR to be merged before proceeding.
The repository is already configured for GitHub Actions to create and approve PRs.
Related Tickets & Documents
Closes #152
Mobile & Desktop Screenshots/Recordings
Steps to QA
I've tested my script, but not the whole flow. We can see how it behaves for a beta release.
Tier (staff will fill in)
[optional] What gif best describes this PR or how it makes you feel?