Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
braintec volunteering
kerrymick organization(s): Kanopi Studios
liber_t volunteering
steveoriol
very_random_man volunteering
ekes organization(s): Open Code
carlosmonroy organization(s): NTT DATA
thejimbirch organization(s): Kanopi Studios
kekkis organization(s): Exove customer(s): City of Tampere
catch organization(s): Third and Grove
grimreaper organization(s): Smile
walli
huzooka organization(s): Munyu customer(s): European Commission and European Union Institutions, Agencies and Bodies
duaelfr volunteering organization(s): Happyculture
herved
ahmad abbad volunteering organization(s): Vardot customer(s): Vardot
rajab natshah organization(s): Vardot customer(s): Vardot
christian.wiedemann organization(s): keytec GmbH & Co. KG
julien tekrane customer(s): European Commission and European Union Institutions, Agencies and Bodies
Git commit message
Commit types
  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.