docs: create Docusaurus unstable docs in minor_version_release workflow #9991
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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
anakin87
requested review from
Amnah199 and
dfokina
and removed request for
a team
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.
Related Issues
Part of https://github.com/deepset-ai/haystack-private/issues/188
Proposed Changes:
Use the script create_unstable_docs_docusaurus.py (introduced in #9980) in minor_version_release workflow.
The workflow is manually triggered when we branch off for a new Haystack release.
With the additions in this PR, the workflow generates unstable docs and creates a PR with them.
How did you test it?
Hard to test it in a realistic scenario without releasing Haystack.
However, I tested it in a simplified way in 9f8ccd5 -> generated PR: #9992
Notes for the reviewer
To minimize the risk of breaking the existing release process, I decided to add new steps to the workflow instead of refactoring the existing ones. I can clearly see some simplification options to adopt when we drop Readme.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.