Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pull request templates

Open
  • Is something wrong?
#36 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
github
Domain
developer-experience, documentation

Research direction

Start by reviewing GitHub's pull request and issue template guidance linked in the issue, then inspect the repository's existing contribution files. Add prompts for the PR's purpose, fixed issue number, and screenshots, and ensure the template files are excluded through .npmignore as requested.

Written by the indexing model from the issue text.

Description

enhancement

Even more so than with issues, I've noticed that PR descriptions are often very sparse.

My hypothesis is that this isn't due to laziness, it's due to a lack of 'inspiration' over what to actually write in the PR description.

Enter pull request (and issue) templates.

This should include:

  • What PR does
  • Issue number it fixes
  • Screenshots

Thanks for the tip @NataliaLKB !

We should also consider adding this to an .npmignore file as it's unnecessary for npm.

Dominant language
No language data
Stars
92
Forks
9
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/contributing

All issues in dwyl/contributing

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.