- Required software: git and node.
- Recommended editor: Visual Studio Code.
- You can also use GitHub Codespaces which sets up everything for you.
- Register a GitHub account.
- Fork this repository under your account.
- Clone the fork onto your machine.
- Open the cloned repository in the code editor.
- Create a git branch (recommended).
- Make your changes and test them locally.
- Commit the changes and push the branch to the remote repo.
- Go to GitHub, and open a pull request, targeting the upstream branch.
- Our standards are pretty low, but make sure the code is not too ugly:
- Run VS Code's autoformat when you're done.
- Check with ESLint by running
npm run lint
, then fix the errors. - Use common sense and follow existing naming conventions.
- Create pull requests for the staging branch, 99% of contributions should go there. That way people could test your code before the next stable release.
- You can still send a pull request for release in the following scenarios:
- Updating README.
- Updating GitHub Actions.
- Hotfixing a critical bug.
- Project maintainers will test and can change your code before merging.
- Write at least somewhat meaningful PR descriptions. There's no "right" way to do it, but the following may help with outlining a general structure:
- What is the reason for a change?
- What did you do to achieve this?
- How would a reviewer test the change?
- Mind the license. Your contributions will be licensed under the GNU Affero General Public License. If you don't know what that implies, consult your lawyer.