GitHub Action to lint Wiki markdown
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, markdown
- Domain
- ci-cd, documentation
Research direction
Start by checking the repository's GitHub Wiki and Actions configuration, then verify whether GitHub Actions can trigger when Wiki pages change. Define how MegaLinter's Markdown checks would run for those updates. Done means Wiki changes reliably trigger the intended Markdown checks.
Written by the indexing model from the issue text.
Description
The Wiki is also a Git project. It would be great to run Markdown lint & other Markdown checks as we now have from MegaLinter. Apparently, it's possible to create a GitHub Action that runs when a Wiki page changes, so it should probably be possible to achieve this.
- Dominant language
- Java
- Stars
- 44
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 3
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.
More from AuthMe/ConfigMe
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
architecture
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100