Repositories Naming Convention
PSI + nome in 🥙 Kebab-case 👉 PSI-il-mio-repository
Commit messages convention
Tutti i messaggi di commit dovrebbero seguire la specifica Conventional Commits
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
- fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
- feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
- BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE >can be part of commits of any type. types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the the Angular convention) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and >others.
es 👉 commit -m 'fix(): bug bla bla bla'
Workflow
Seguire GitHub flow o Git flow
