Releasey: Automatically create PRs for documentation updates
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 137
Description
### Is your feature request related to a problem? Please describe.
The manual steps described by #3476 can be automated and added to either the 3rd or 4th releasey workflow, to let the workflow create the PRs against the `versioned-docs` and `main` branches.
### Describe the solution you'd like
_No response_
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reading issue #3476 and locating the 3rd and 4th Releasey workflows in the repository. Trace the existing manual documentation-update steps and determine how PRs should be created against the versioned-docs and main branches; done means the selected workflow creates both PRs reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100