Skip to content

Commit 0273d22

Browse files
committed
📝(doc) complete contributing policy
We made mandatory signing commits. Provided warnings for common gitmoji errors Signed-off-by: virgile-deville <[email protected]>
1 parent e9ab099 commit 0273d22

File tree

2 files changed

+22
-7
lines changed

2 files changed

+22
-7
lines changed

CHANGELOG.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ and this project adheres to
1111
## Added
1212

1313
- 🚩 add homepage feature flag #861
14+
- 📝(doc) update contributing policy (commit signatures are now mandatory) #895
1415

1516

1617
## [3.1.0] - 2025-04-07

CONTRIBUTING.md

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,16 @@
22

33
Thank you for taking the time to contribute! Please follow these guidelines to ensure a smooth and productive workflow. 🚀🚀🚀
44

5-
To get started with the project, please refer to the [README.md](https://github.com/suitenumerique/docs/blob/main/README.md) for detailed instructions.
5+
To get started with the project, please refer to the [README.md](https://github.com/suitenumerique/docs/blob/main/README.md) for detailed instructions on how to run Docs locally.
66

7-
Contributors are required to sign off their commits with `git commit --sign-off`: this confirms that they have read and accepted the [Developer's Certificate of Origin 1.1](https://developercertificate.org/).
7+
Contributors are required to sign off their commits with `git commit --signoff`: this confirms that they have read and accepted the [Developer's Certificate of Origin 1.1](https://developercertificate.org/). For security reasons we also require [signing your commits with your SSH or GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification) with `git commit -S`.
88

99
Please also check out our [dev handbook](https://suitenumerique.gitbook.io/handbook) to learn our best practices.
1010

1111
## Help us with translations
1212

1313
You can help us with translations on [Crowdin](https://crowdin.com/project/lasuite-docs).
14-
Your language is not there? Request it on our Crowdin page 😊.
14+
Your language is not there? Request it on our Crowdin page 😊 or ping us on [Matrix](https://matrix.to/#/#docs-official:matrix.org) and let us know if you can help with translations and/or proofreading.
1515

1616
## Creating an Issue
1717

@@ -35,10 +35,14 @@ All commit messages must adhere to the following format:
3535

3636
`<gitmoji>(type) title description`
3737

38-
* <**gitmoji**>: Use a gitmoji to represent the purpose of the commit. For example, ✨ for adding a new feature or 🔥 for removing something, see the list here: <https://gitmoji.dev/>.
38+
* <**gitmoji**>: Use a gitmoji to represent the purpose of the commit. For example, ✨ for adding a new feature or 🔥 for removing something, see the list [here](https://gitmoji.dev/).
3939
* **(type)**: Describe the type of change. Common types include `backend`, `frontend`, `CI`, `docker` etc...
40-
* **title**: A short, descriptive title for the change.
41-
* **description**: Include additional details about what was changed and why.
40+
* **title**: A short, descriptive title for the change
41+
42+
**⚠️ Make sure you add no space between the emoji and the (type) but add a space after the closing parenthesis of the type and use no caps!**
43+
* **description**: Include additional details on why you made the changes.
44+
45+
**⚠️ Commit description message are mandatory and shouldn't be too long**
4246

4347
### Example Commit Message
4448

@@ -66,7 +70,9 @@ Please add a line to the changelog describing your development. The changelog en
6670
It is nice to add information about the purpose of the pull request to help reviewers understand the context and intent of the changes. If you can, add some pictures or a small video to show the changes.
6771

6872
### Don't forget to:
69-
- check your commits
73+
- signoff your commits
74+
- sign your commits with your key (SSH, GPG etc.)
75+
- check your commits (see warnings above)
7076
- check the linting: `make lint && make frontend-lint`
7177
- check the tests: `make test`
7278
- add a changelog entry
@@ -86,3 +92,11 @@ Make sure that all new features or fixes have corresponding tests. Run the test
8692
If you need any help while contributing, feel free to open a discussion or ask for guidance in the issue tracker. We are more than happy to assist!
8793

8894
Thank you for your contributions! 👍
95+
96+
## Contribute to BlockNote
97+
We use [BlockNote](https://www.blocknotejs.org/) for the text editing features of Docs.
98+
If you find and issue with the editor you can [report it](https://github.com/TypeCellOS/BlockNote/issues) directly on their repo.
99+
100+
Please consider contributing to BlockNotejs, as a library, it's useful to many projects not just Docs.
101+
102+
The project is licended with Mozilla Public License Version 2.0 but be aware that [XL packages](https://github.com/TypeCellOS/BlockNote/blob/main/packages/xl-docx-exporter/LICENSE) are dual licenced with GNU AFFERO GENERAL PUBLIC LICENCE Version 3 and proprietary licence if you are [sponsor](https://www.blocknotejs.org/pricing).

0 commit comments

Comments
 (0)