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

tldr;

Open
  • Is something wrong?
#28 5 comments 2 reactions 1 assignee View on GitHub

@iteles is already working on this.

Since Jul 30, 2017.

Assessment

This issue has not been assessed yet.

Description

awaiting-review enhancement starter T1h

These are the things I feel like shouting at people. The things that get done for the first couple of weeks and then fall by the wayside and that can't happen. The things I remind people to do over and over again but seem to only be done to varying degrees and by a handful of people:

  • Create an issue before you start working on anything
    • Discuss your proposed implementation in that issue
    • Add a time estimate to it
  • Once there is at least one comment agreeing the feature is needed, start working on it _by adding to the readme _first**
  • Link all commits to a relevant issue
  • Each PR should:
    • Solve only one problem: fix one bug, implement one small feature or part thereof
    • Have a clear and simple description which also links to the issue it solves
    • Add to the documentation or explain why it shouldn't
    • Include full tests for any code that is introduced
    • Be assigned to the designated QA when ready for review

Adds to #12

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.