tildefriends/docs/contributing.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

61 lines
1.2 KiB
Markdown
Raw Normal View History

2024-05-11 13:47:14 -04:00
# How to contribute
2024-05-12 05:20:09 -04:00
## Philosophy
TODO
## Best practices
TODO
## How to get your changes merged
2024-05-11 13:47:14 -04:00
- Fork this repository
- Clone your repository
2024-05-12 03:04:52 -04:00
1. Alternatively, you can add a remote called `fork`:
2024-05-11 13:47:14 -04:00
2024-05-12 04:57:39 -04:00
`$ git remote add fork https://dev.tildefriends.net/YOUR_USERNAME/tildefriends.git`
2024-05-12 03:04:52 -04:00
You'll need to set your branch's upstream to `fork`:
2024-05-12 04:57:39 -04:00
`$ git push --set-upstream fork my-branch`
2024-05-12 03:04:52 -04:00
2. or you can change the `origin` remote on your existing clone altogether:
2024-05-12 04:57:39 -04:00
`$ git remote set-url origin https://dev.tildefriends.net/YOUR_USERNAME/tildefriends.git`
2024-05-11 13:47:14 -04:00
- Make your changes
- I want to edit C code !
2024-05-11 13:47:14 -04:00
2024-05-11 15:22:25 -04:00
TODO
- I want to edit JavaScript code !
2024-05-11 13:47:14 -04:00
2024-05-11 15:22:25 -04:00
TODO
- I want to write documentation !
2024-05-11 13:47:14 -04:00
Great! Before you do, have a look at the [documentation guidelines](guidelines/documentation-guidelines.md) to learn how to write consistent documentation.
2024-05-11 15:22:25 -04:00
In all cases:
- Make sure that your commit messages are descriptive.
<!-- - hi -->
2024-05-11 15:22:25 -04:00
2024-05-11 13:47:14 -04:00
- Format your changes:
If you've edited C code: run `make format`
If you've edited JavaScript code or the documentation: run `npm run format`
- Open a pull request
TODO
- Get your changes reviewed and merged
TODO