There's less than 10 days until Hacktoberfest finishes. If you're still looking for projects to contribute to, look no further than GitHub's own open source projects 👀
There are three main open source GitHub projects you can contribute to, which count towards Hacktoberfest. They are the GitHub Docs, GitHub CLI, and GitHub Hackathons. Let's take a look.
GitHub Docs
Yes, you heard that correctly. The GitHub Docs are open source!
GitHub Docs
This repository contains the documentation website code and Markdown source files for docs.github.com.
GitHub's Docs team works on pre-production content in a private repo that regularly syncs with this public repo.
Use the table of contents icon 
on the top left corner of this document to get to a specific section of this guide quickly.
Contributing
See the contributing guide for detailed instructions on how to get started with our project.
We accept different types of contributions, including some that don't require you to write a single line of code.
On the GitHub Docs site, you can click the make a contribution button at the bottom of the page to open a pull request for quick fixes like typos, updates, or link fixes.
For more complex contributions, you can open an issue using the most appropriate issue template to describe the changes you'd like to see.
…
Open source isn't all about coding. here's lots of ways you can contribute to open source without writing lines of code. Documentation is one of those ways to contribute.
The GitHub Docs repo contains all the documentation relating to GitHub's products and features. We open sourced our docs last year as a way for developers to shape the documentation they use everyday.
If you're reading the docs, and you notice something you'd like to change or improve, you can do so. Fork the repo, and head to the the folder with all our documentation. From here, make your changes and submit your PRs.
Other ways to contribute to docs
Remember, whilst open source isn't all about writing lines of code, it doesn't have to be about writing documentation either. If writing documentation isn't your thing, you can still be involved in shaping the GitHub docs.
Jump over to the Discussions and engage with the community. You can make suggestions, provide feedback, or just be part of the conversation.
You can also open an issue if you'd like to report anything, contact our support team, or be a project owner. Good documentation needs good feedback and collaboration too!
GitHub CLI
If coding is your jam, then maybe you'd like to contribute to the GitHub CLI.
GitHub CLI
gh is GitHub on the command line. It brings pull requests, issues, and other GitHub concepts to the terminal next to where you are already working with git and your code.
GitHub CLI is available for repositories hosted on GitHub.com and GitHub Enterprise Server 2.20+, and to install on macOS, Windows, and Linux.
Documentation
For installation options see below, for usage instructions see the manual.
Contributing
If anything feels off, or if you feel that some functionality is missing, please check out the contributing page. There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.
If you are a hubber and are interested in shipping new commands for the CLI, check out our doc on internal contributions.
Installation
macOS
gh is available via Homebrew, MacPorts, Conda, Spack, and as a…
The GitHub CLI brings GitHub to your command line. It includes issues, PRs, repo management, and more. If you see bugs that need fixing, you've suggested a feature that's been approved, or you want to update documentation, jump in and create your PRs! You can also be part of the community by opening an issue to report bugs, suggest features, or proposes changes.
Now with CLI version 2.0, there's the new extensions. You can practically create anything you like, or search the multitude of extensions already created by the community. This is a great opportunity to explore the CLI and contribute to the way developers interact with GitHub in the terminal.
GitHub Hackathons
Hackathons are key events in the developer community. Whether it's online like Hacktoberfest, or IRL (when we're allowed to), hackathons help drive the ecosystem. That's why we developed a repo with lots of information on how to run a hackathon. There's also tips, tricks, and resources for anyone looking to plan, organise, or execute a hackathon.
github
/
hackathons
Tips, Tricks, and Resources for running your hackathon.
JOIN A COMMUNITY CONNECTED BY CODE
This repository contains Tips, Tricks, and Resources to help you plan, organise, and execute your hackathons. You can use these to help guide you when planning your next hackathon.
There are three main sections to this repository:
Guidelines are detailed below on how to contribute to each of these documents. If there are other issues you'd like to flag, please open an issue.
Participating in a hackathon
Please note this repository is NOT geared towards participants. This repository contains information useful to hackathon organisers and managers. It does not contain tips/tricks or resources for participating in a hackathon. If you are looking for a hackathon to participate in, you can check out the following sites:
- Major League Hacking
- DevPost
- Hackathons International
- Hackaday
- DevFolio
- Hack Club
- HackaList
- AngelHack
- Hackathon IO
Organisers, the above sites are great…
If you'd like to contribute resources, check out the Resources page and submit a PR. You can also get involved with the community by engaging in the Discussions, or opening an issue if you'd like to flag something with us.
Hackathon organisers who have events for Hacktoberfest might find this repo useful in producing your hack!
Get involved in open source
Check out these open source GitHub projects and be part of the magic that brings developers together 🔮 No matter which project you decide to contribute to, whether it's one of the three here or something else entirely, don't forget to read the contribution guidelines.
Happy hacking 🎃
Top comments (2)
I did a fork of existing gh-gitignore extension and did a rework. Is my fork participant of gh-extension topic list or not?
You'll need to double check that the gh-extension tag is still in the repo. Do you have a link?