bazelbuild / bazelbuild/rules_license
Turn on github pages to hold end user documentation
Open
P3
- Dominant language
- Starlark
- Stars
- 85
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Do we user a `docs` branch or keep in main?
Contributor guide
Research direction
Start by reviewing the repository's current branch layout and the GitHub Pages settings. Compare the proposed docs branch with keeping documentation in main, then document the chosen source and publishing path. Done means the end-user documentation has a clear home and can be published through GitHub Pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100