All code is created according to the conventions of FDND Agency.
Use the development tool for creating new branches. Here Github automatically creates a new branch from a created issue.
This tool can be seen in the right column menu of an issue.
The name of a branch is: issueNumber-issue-title
"At FDND Agency, because of Semantic Versioning, we use conventional commits. Conventional commit is a specification, a set of rules that have to be followed when writing commit messages."
Allowed Commit types:
build: ... Changes that affect the build system or external dependencies
chore: ... Changes to the build process or auxiliary tools and libraries such as documentation generation
ci: ... Changes to CI configuration files and scripts (GitHub Actions, netlify.toml)
docs: ... Changes to documentation, eg: Readme.md, Handover.md or Figma files or design rationale in the Wiki
feat: ... Implementing a new feature
fix: ... Fix for a bug, style or layout issue
perf: ... A code change that improves performance
refactor: ... A code change that neither fixes a bug nor adds a feature but improves structure or readability
style: ... Changes that affect readability but not the working of the code (source formatting, adding tabs or newline)
test: ... Adding missing or correcting existing tests
Bron: Conventional conventions - FDND Agency conventions
Use the pull request template which you automagically get when creating a PR in one of our repositories.
Please make sure you follow the following rules:
- Write small PR's
- Review your own PR first
- Provide context and guidance
Bron: Pull request - FDND Agency conventions