Documentation CI/CD stability and QoL improvements
Open
Nobody has claimed this yet.
epic
internal
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Documentation CI/CD stability and quality-of-life improvements.
- https://github.com/tarantool/doc/issues/3234
- https://github.com/tarantool/doc/issues/3237
- https://github.com/tarantool/doc/issues/3238
- Use fail-fast options in documentation build and deployment scripts
- Report failures in doc projects to a VK Teams chat
- Update all doc projects to the newest version of tarantool/doc-builder
- https://github.com/tarantool/doc/issues/2443
Template for subtasks:
- [ ] [tarantool/doc@`latest`](https://github.com/tarantool/doc/tree/latest)
- [ ] [tarantool/doc@`tt`](https://github.com/tarantool/doc/tree/tt)
- [ ] https://github.com/tarantool/enterprise_doc/tree/master
- [ ] https://github.com/tarantool/tdg-doc/tree/latest (2.x)
- [ ] https://github.com/tarantool/tdg-doc/tree/master (1.x)
- [ ] https://github.com/tarantool/tarantool-internals/tree/master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked subtasks 3234, 3237, 3238, and 2443, then inspect the documentation build and deployment scripts across the listed projects. Done means completing the unchecked stability, VK Teams reporting, and doc-builder update tasks and recording progress for each project.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100