maliput / maliput/maliput_documentation
Explain how to add a new repository to the workspace
- Dominant language
- CMake
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Things to watch out:
- In case it uses other private projects from the workspace, it should add the MALIPUT_TOKEN
- In case it requires CI, we should try to copy the workflows we already have to provide support for gcc, clang, and scan-build
- Naming conventions
- etc
Contributor guide
Research direction
Review the existing workspace repository documentation and CI workflows first, especially the examples supporting gcc, clang, and scan-build. Document the steps for adding a repository, including private-project access with MALIPUT_TOKEN, CI coverage, and naming conventions; the documentation should also explain any remaining workspace-specific considerations.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100