➕ (repo): Add gitmoji [DSDK-188]

[valpinkman]

DSDK-188 setup git conventions

📝 Description

Add Gitmoji as our new git conventions
Add a commit script to run from the root folder => pnpm commit

❓ Context

• JIRA or GitHub link: DSDK-188

✅ Checklist

Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

• Covered by automatic tests.
• Impact of the changes:
  • Adds a new dependency + a script to use it

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
device-sdk-ts-sample	❌ Failed (Inspect)			Feb 13, 2024 2:51pm

[aussedatlo]

So the new convention for PR title is <emoji> (<ticket>): <description> ?

[valpinkman]

So the new convention for PR title is <emoji> (<ticket>): <description> ?

Right now i'm testing the CLI to see what it has to offer, but it seems that if we want to keep the ticket in the title we could use it in the scope, or we keep scope as it is and we just append the ticket number at the end of the commit ?

@aussedatlo @ofreyssinet-ledger @jdabbech-ledger @jiyuzhuang

---

Possible format

• ➕ (repo): Add gitmoji DSDK-188
• ➕ (DSDK-188): Add gitmoji
• ➕ Add gitmoji

[aussedatlo]

LGTM 👍

[jiyuzhuang]

So the new convention for PR title is <emoji> (<ticket>): <description> ?

Right now i'm testing the CLI to see what it has to offer, but it seems that if we want to keep the ticket in the title we could use it in the scope, or we keep scope as it is and we just append the ticket number at the end of the commit ?

@aussedatlo @ofreyssinet-ledger @jdabbech-ledger @jiyuzhuang

Possible format

• ➕ (repo): Add gitmoji DSDK-188
• ➕ (DSDK-188): Add gitmoji
• ➕ Add gitmoji

Thank you for your work @valpinkman. In my opinion, I prefer the second one, but can we do some adaptions like:
[DSKD-123] 🍀 Make the project great(one space between scope and emoji, one space between emoji and commit message). Reasons below:

1. Brackets seem more strict than parentheses(maybe a personal sentiment);
2. Colon is not necessary because the ] or ) if you did not agree with the first point has already separate the ticket ID and the emoji.

[aussedatlo]

Using gitmoji scope option, the output will automatically be formatted as <emoji> (<scope>): <message>. If we want to use custom format, I'm afraid we will need to do it ourselves without scope gitmoji option. 😢

[valpinkman]

Using gitmoji scope option, the output will automatically be formatted as <emoji> (<scope>): <message>. If we want to use custom format, I'm afraid we will need to do it ourselves without scope gitmoji option. 😢

exactly this ^