Create a CONTRIBUTING.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by checking the repository structure and any existing contribution or branch-protection guidance before creating CONTRIBUTING.md. Document how contributors provide DCO signoff and enable the DCO app for the appropriate branches; done means both requested items are covered and the file is present at the repository root.
Written by the indexing model from the issue text.
Description
- Describes how one can contribute to the project with DCO signoff.
- Enable DCO app for appropriate branches.
- Dominant language
- Ruby
- Stars
- 0
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 MicroShed/MicroShed.github.io
-
MicroShed/MicroShed.github.io#8 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in MicroShed/MicroShed.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
simp/pupmod-simp-simp#395 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
simp/pupmod-simp-rsyslog#219 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
simp/pupmod-simp-pupmod#256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
simp/pupmod-simp-sudo#150 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100