Create Blogpost PR Template and Docs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github
- Domain
- documentation
Research direction
Start with the linked GitHub Docs guidance on pull request templates, then locate the repository's blog post author documentation and existing template conventions. Add a blog-post PR template covering PR naming, required information, labels, and any agreed review contact, and document how authors use it to create a PR.
Written by the indexing model from the issue text.
Description
Task
Create a PR template (see GitHub Docs) for new blog posts. This template should include guidance on naming the PR, which information to provide, and which labels to add.
Further, add information to the blog post author docs on how to create a new PR with the template.
The PR template could also include which to ping for review. However, that's always hard due to fluctuation. Maybe a GitHub team would be the better choice as that can be pinged and allows reaching the currently active contributors of that field (if the teams are properly managed).
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 17
- 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 MovingBlocks/movingblocks.github.com
-
bug help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
MovingBlocks/movingblocks.github.com#238 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Good First Issue help wanted question
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MovingBlocks/movingblocks.github.com#214 · 2 comments ·
All issues in MovingBlocks/movingblocks.github.com
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100