Move PULL_REQUEST_TEMPLATE.md from root to .github
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github
- Domain
- tooling
Research direction
Start with PULL_REQUEST_TEMPLATE.md at the repository root and the .github directory. Move the template into .github, then verify that the repository still uses it as its pull request template.
Written by the indexing model from the issue text.
Description
Context
PULL_REQUEST_TEMPLATE.md is GitHub-specific code and thus probably better placed in the .github folder
- Dominant language
- JavaScript
- Stars
- 257
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
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 WDscholia/scholia
-
aspects bug P108-employer P1416-affiliation P361-part-of
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug
All issues in WDscholia/scholia
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·