Community

Mailing List

General questions or comments for the Git community can be sent to the mailing list by using the email address git@vger.kernel.org.

If you wish to report any possible bug for Git, please use this mailing list as well.

You do not need to subscribe: you will be Cc'd in replies. Please keep the Cc list intact when replying (use "Reply to all"). Greylisting may delay your first post for a few hours. Note also that the list only accepts plain-text email; please disable HTML in your outgoing messages.

By subscribing (click here), you can make sure you're not missing follow-up discussions and you can also learn about other development in the community. The list archive can be found on public-inbox.

Windows-specific questions can also be sent to the Git for Windows mailing list (if in doubt whether your question is Windows-specific, just use the general Git mailing list). Please submit Windows-specific bugs to Git for Windows' bug tracker.

There is also Git user mailing list on Google Groups which is a nice place for beginners to ask about anything. If you're a downstream packager of Git, consider joining the Git packagers mailing list for low-volume announcements from the developers, as well as other discussion related to packaging & porting Git.

Bug Reporting

Bugs in git can be reported directly to the mailing list (see above for details). Note that you do not need to subscribe to the list to send to it. You can help us out by attempting to reproduce the bug in the latest released version of git, or if you're willing to build git from source, the next branch. Sometimes an attempted fix may be pending in this branch, in which case your feedback as to whether the fix worked for you will be appreciated.

If you are using git 2.27.0 or later, you can run git bugreport in the repository where you observed the bug, which generates a template to guide you through writing a useful bug report and gathers some diagnostic information about your environment.

Bugs related to this website can be reported at its issue tracker. Bugs related to the content of the "Pro Git" book can be reported at its issue tracker.

If you are new to submitting bugs, you might find this guide helpful for producing useful bug reports.

Reporting Security Issues

Issues which are security relevant should be disclosed privately to the Git Security mailing list.

IRC Channel

If the manpages and this book aren’t enough and you need in-person help, you can try the #git channel on the Libera Chat IRC server (irc.libera.chat). These channels are regularly filled with hundreds of people who are all very knowledgeable about Git and are often willing to help. The #git-devel channel welcomes Git development discussion, and might be able to help you contribute to Git.

If you need specific help about one of the for-profit Git hosting sites, you might try their own IRC channels (such as #github or #gitlab) on the same IRC server.

There is a monthly community newsletter called "Git Rev News", with its archive and its latest edition. Information on how to subscribe can be found on the dedicated webpage.

Contributing to Git

The Documentation directory in the Git source code has several files of interest to developers who are looking to help contribute. After reading the coding guidelines, you can learn how to submit patches. If you are just starting out, you can read the My First Contribution tutorial. For those looking to get more deeply involved, there is a howto for Git maintainers.

The Git Developer Pages have a Hacking Git page which lists useful development resources. They also have information for people applying to work on Git as part of programs like Outreachy or the Google Summer of Code.