CI/CD for documentaiton
Open
documentation
- Dominant language
- JavaScript
- Stars
- 543
- Forks
- 117
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 2
Description
We have a few open PRs related to the docs:
- #399
- #400
- #401
- #405
I think it would be safer and easier if we have a CI that runs the hexo documentation build so we can easily review/merge these PRs, I think this would be a low-hanging fruit with GitHub actions.
Contributor guide
Research direction
Review the open documentation PRs #399, #400, #401, and #405, then identify how the Hexo documentation build is run. Define a GitHub Actions check that runs that build for documentation changes; done means the workflow can validate these PRs before they are merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100