Skip to content

Latest commit

 

History

History
41 lines (24 loc) · 2.58 KB

File metadata and controls

41 lines (24 loc) · 2.58 KB

Contributing to HACKccessibility-expose-the-documentation

Thank you for your interest in contributing to HACKccessibility-expose-the-documentation 🎉!

HACKccessibility-expose-the-documentation is about building a wizard to help writing documentation lately.

Please read the contribution guidelines to achieve the best interaction with the community.

Participation guidelines

This project adheres to a code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to user701@orange.fr .

What we're working on

Take a look at the issues in our current milestone or browse some good first bugs to get started!

How to submit changes

Explain how you want contributors to propose changes. For an example GitHub workflow, see Node.js's instructions for code contributions.

Once you've identified one of the issues above that you feel you can contribute to, you're ready to make a change to the project repository!

  1. Fork this repository. This makes your own version of this project you can edit and use.
  2. Make your changes! You can do this in the GitHub interface on your own local machine. Once you're happy with your changes...
  3. Submit a pull request. This opens a discussion around your project and lets the project lead know you are proposing changes.

First time contributing to open source? Check out this free series, How to Contribute to an Open Source Project on GitHub.

How to report bugs

Notice a mistake? Please file any bugs, requests, or questions in our issue tracker!

Communication channels

During development sprints, a conf'call channel will be available. Join the conf'call.