Thanks for your interest in contributing. Here are some common scenarios for what you may want to contribute to.
- Feel free to post your question on our Discourse or join our Matrix Support Channel.
-
Ensure the bug wasn't already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to use one of the templates we provide if your request applies to them. If not, use the 'Question / Other' template.
-
Open a new GitHub pull request with the patch.
-
Ensure the PR description is precise about the problem and your solution. Just fill out our template. That should cover the most important information.
- Suggest your idea in the HedgeDoc Dev Channel and start writing code. Our maintainers and other project developers can provide useful details about the architecture and show you relevant issues and discussions.
If you want to improve a translation or add a new translation altogether, we handle those via POEditor.
HedgeDoc is a volunteer effort. We encourage you to pitch in and to help us making this project even better.
Thanks! ❤️ ❤️ ❤️
By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. The DCO is a legally binding statement, please read it carefully.
If you can certify it, then just add a line to every git commit message:
Signed-off-by: Jane Doe <[email protected]>
Use your real name (sorry, no pseudonyms or anonymous contributions).
If you set your user.name
and user.email
git configs, you can sign your commit automatically with git commit -s
.
You can also use git aliases like git config --global alias.ci 'commit -s'
.
Now you can commit with git ci
and the commit will be signed.