CONTRIBUTING.md

[zatramanh56789]

Contributing to training-kit

🎉 Thank you for taking the time to contribute and for seeking out these instructions. We ❤️ community contributions to these materials.

---

Code of Conduct

This project and everyone who participates in it is governed by the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

---

What should I know before I get started?

The goal of these resources

These materials are designed to help those new to Git, GitHub and software development as a whole. By using these materials, we hope users will:

• Feel welcome and become active contributors in the open source community
• Learn best practices for using Git and GitHub
• Learn how to use the applications within GitHub's ecosystem to build better software

Types of contributions we love

We're always looking for contributions to help improve these resources. This includes:

• Improving the existing cheat sheets
• Translations of existing cheat sheets into new languages
• Adding new courseware or resources aligned with the goals

---

How to contribute

Report a bug

Oops, thanks for finding that! If you know how to fix it, please feel free to fork the repository and submit a change via Pull Request.

If you aren't sure how to fix it or just don't have time, we invite you to open a new Issue. Please be sure to provide information, so we can recreate the error.

Translate existing resources

Several community members have been kind enough to translate the Git Cheat Sheets into various languages. At this time, we are only set up to serve the cheat sheets in various languages (but maybe you can help us change that 😉). If you are planning to contribute a translation, please do the following:

• Fork this repository
• Create a new folder in the downloads directory using the standard abbreviation for the language you are providing.
• Copy the most recent English version of the cheat sheet to the folder you created.
• Complete the translation
• Add a link to the translated resource on /index.html
• Open a pull request against the main branch of this repository.
• Be sure to @ mention a couple of your friends who are native speakers and ask them to review the translation.
• Update your translation based on feedback from your friends.

When this process is complete, we will be happy to merge the completed document.

Contribute something new

Whether you have an idea to make it better, or want to contribute a whole new course or resource ... we ❤️ new ideas! We invite you to open a new Issue to talk about it before you invest too much time. Of course, if you want to experiment first, you can fork this repository and submit your idea via a Pull Request.

When you are contributing something new, we ask you to be familiar with our content philosophy, the structure of the repository, and building Jekyll sites locally. See the sections below for more information.

Not sure where to start?

If you just want to help out, but don't have a particular change in mind, check out the open issues for projects you can tackle, review an open pull request, or check out the project ROADMAP.

---

Styling content

This site uses GitHub's CSS toolkit called Primer. It's easy to use, and if your contribution requires some design or front-end work you should check out the Primer Docs.

For writing style guides, we lean on the GitHub Brand Guide. The Content section is a great place to start.

Building and testing

When you are ready to test your changes, you will want to build the repository locally. This is fully automated through a series of shell scripts based the scripts to rule them all!

To build the materials do the following:

1. Run script/bootstrap to install the dependencies
2. Run script/build to build the site
3. Run script/server
   • When successful, the script will initiate a local server at http://127.0.0.1:4000/.
4. Simply paste that into your favorite web-browser, and you will be ready to test