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

Example of a Terrible Pull Request (Worst Case Scenario)

Open
  • Is something wrong?
#78 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
github
Domain
documentation

Research direction

Read the Contributing Guide and inspect the DWYLBOT behavior described in the issue. The issue does not identify a target file, requested edit, or acceptance criteria, so the intended documentation change and definition of done need clarification before work can begin.

Written by the indexing model from the issue text.

Description

bug discuss

This person has not followed a single step in the Contributing Guide... 😢
how-not-to-do-a-pull-request
It's clear they either have limited GitHub Experience or that they are used to working alone.
Either way this is a communication and teamwork antipattern that must be avoided.

After committing directly to master this is the next worst thing. 😞

🤖 DWYLBOT will reject this kind of Pull Request by leaving a comment advising the person to view the Contributing Guide.

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 Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.