starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-24 21:36:01 +03:00

[GH-ISSUE #267] [DOC-295] Add commitlint for linting of commit messages #72

New issue

Closed

opened 2026-02-26 18:45:14 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:45:14 +03:00

Owner

Originally created by @Mythie on GitHub (Aug 18, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/267

As the project grows we need to work on enforcing consistency across various processes, one of these areas is commit messages and formatting.

To handle this we would like to use commitlint in combination with husky (which is already in the repo). Using commitlint we would like to enforce conventional commits which will require that commits be labelled based on the kind of change they are.

This change will help align the way we contribute to the project and also allow niceties with other tools for automated release notes and versioning.

Implementation of this change should be fairly straightforward, from memory there is a quick start that will assist with the implementation of most of this without any real trouble.

_{From SyncLinear.com | DOC-295}

Originally created by @Mythie on GitHub (Aug 18, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/267 As the project grows we need to work on enforcing consistency across various processes, one of these areas is commit messages and formatting. To handle this we would like to use [commitlint](https://github.com/conventional-changelog/commitlint) in combination with [husky](https://github.com/typicode/husky) (which is already in the repo). Using commitlint we would like to enforce [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) which will require that commits be labelled based on the kind of change they are. This change will help align the way we contribute to the project and also allow niceties with other tools for automated release notes and versioning. Implementation of this change should be fairly straightforward, from memory there is a quick start that will assist with the implementation of most of this without any real trouble. <sub>From [SyncLinear.com](https://synclinear.com) | [DOC-295](https://linear.app/documenso/issue/DOC-295/add-commitlint-for-linting-of-commit-messages)</sub>

kerem

2026-02-26 18:45:14 +03:00

closed this issue
added the
💎 Bounty

💰 Rewarded
labels

kerem commented

2026-02-26 18:45:14 +03:00

Author

Owner

@Mythie commented on GitHub (Aug 18, 2023):

/bounty 100

@Mythie commented on GitHub (Aug 18, 2023): /bounty 100

kerem commented

2026-02-26 18:45:14 +03:00

Author

Owner

@algora-pbc[bot] commented on GitHub (Aug 18, 2023):

~~💎 $100 bounty created by Mythie~~
~~🙋 If you start working on this, comment /attempt #267 to notify everyone~~
~~👉 To claim this bounty, submit a pull request that includes the text /claim #267 somewhere in its body~~
~~📝 Before proceeding, please make sure you can receive payouts in your country~~
~~💵 Payment arrives in your account 2-5 days after the bounty is rewarded~~
~~💯 You keep 100% of the bounty award~~
~~🙏 Thank you for contributing to documenso/documenso!~~

Attempt	Started (GMT+0)	Solution
🟢 @Ashutosh-Bhadauriya	Aug 18, 2023, 5:33:06 AM	#270

@algora-pbc[bot] commented on GitHub (Aug 18, 2023): ~~💎 **$100** bounty created by Mythie~~ ~~🙋 If you start working on this, comment `/attempt #267` to notify everyone~~ ~~👉 To claim this bounty, submit a pull request that includes the text `/claim #267` somewhere in its body~~ ~~📝 Before proceeding, please make sure you can [**receive payouts**](https://docs.algora.io/bounties/payments#country-support) in your country~~ ~~💵 Payment arrives in your account 2-5 days after the bounty is rewarded~~ ~~💯 You keep 100% of the bounty award~~ ~~🙏 Thank you for contributing to documenso/documenso!~~ | Attempt | Started (GMT+0) | Solution | |---|---|---| | 🟢 @Ashutosh-Bhadauriya | Aug 18, 2023, 5:33:06 AM | [#270](https://github.com/documenso/documenso/pull/270) |

kerem commented

2026-02-26 18:45:15 +03:00

Author

Owner

@Ashutosh-Bhadauriya commented on GitHub (Aug 18, 2023):

@Mythie I would like to take this 🙂
/attempt #267

Options

Cancel my attempt

@Ashutosh-Bhadauriya commented on GitHub (Aug 18, 2023): @Mythie I would like to take this 🙂 /attempt #267 <details id="algora-options"> <summary>Options</summary> <ul> <li> <a href="https://console.algora.io/api/bounties/cllg5cv2r0002la0f7q063vr2/cancel-attempt"> Cancel my attempt </a> </li> </ul> </details>

kerem commented

2026-02-26 18:45:15 +03:00

Author

Owner

@algora-pbc[bot] commented on GitHub (Aug 18, 2023):

💡 @Ashutosh-Bhadauriya submitted a pull request that claims the bounty. You can visit your org dashboard to reward.

@algora-pbc[bot] commented on GitHub (Aug 18, 2023): 💡 @Ashutosh-Bhadauriya submitted a [pull request](https://github.com/documenso/documenso/pull/270) that claims the bounty. You can [visit your org dashboard](https://console.algora.io/org/documenso/bounties) to reward.

kerem commented

2026-02-26 18:45:15 +03:00

Author

Owner

@algora-pbc[bot] commented on GitHub (Aug 18, 2023):

🎉🎈 @Ashutosh-Bhadauriya has been awarded $100! 🎈🎊

@algora-pbc[bot] commented on GitHub (Aug 18, 2023): 🎉🎈 @Ashutosh-Bhadauriya has been awarded **$100**! 🎈🎊

kerem referenced this issue

2026-02-26 18:48:41 +03:00

[PR #72] [CLOSED] Show Completed Date for Documents #733

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#72

No description provided.

Rows
Columns