Permet la création de compte d'administrateur pour ajouter/editer/supprimer tout ou partie d'une gestion d'ingrédients classé par étapes et catégories afin de créer des compositions de Pizza et pouvoir les mettres ensuite à disposition à l'achat pour l'application de commande (Projet Android [url] ).
Make sure that your commits in the pull request follow the conventional commits specification, as a GitHub action will check if the spec is respected.
Conventional Commit is a standardized commit message format that promotes consistency and simplifies the process of generating changelogs, versioning, and navigating through project history. It follows a structured format consisting of a type, an optional scope, a description, and optional body and footer.
Here is a list of common commit types:
-
feat: A new feature. -
fix: A bug fix. -
docs: Changes to documentation. -
style: Changes to code style (formatting, indentation, etc.). -
refactor: Refactoring code without changing its behavior. -
perf: Performance improvements. -
test: Adding, modifying, or fixing tests. -
build: Changes affecting the build system or external dependencies. -
ci: Changes to CI/CD configuration files and scripts. -
chore: Other changes that don't modify the src or test files.
Examples of conventional commit messages:
feat: Add new login functionality
fix: Correct typo in homepage title
docs: Update README with new project setup instructions
style: Reformat code for better readability
refactor: Simplify logic in the search function
Remember that the goal of conventional commit is to make commit messages more informative and easier to understand, so try to keep your descriptions clear and concise.