Issue
Contribution records
Contributors

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

Give credit to everyone
g4mbini volunteering organization(s): Dropteam, Alliance of Digital Builders (AODB)
pdureau
grimreaper volunteering organization(s): Smile
ivan zugec
rajab natshah organization(s): Vardot customer(s): Vardot
sharique
mogtofu33 organization(s): Beyris
lsmith77
fboulanger
dhansen
just_like_good_vibes
monet-fort
christian.wiedemann organization(s): keytec GmbH & Co. KG
d34dman volunteering organization(s): Factorial.io, Digitwings
shanekba
jogordon
echechulina
juc1
bacarndiaye
maboy organization(s): Smile
nkarhoff
yannickoo organization(s): 1xINTERNET
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.