Issue
Contribution records
Contributors

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

Give credit to everyone
renrhaf organization(s): SaaS Production customer(s): Les Décideurs
nicobot organization(s): Front ID
jeroent organization(s): iO
fractile81 organization(s): Miles
recrit
jlenni
kimberleycgm organization(s): Zoocha
jjcarrion organization(s): Digitalist
rondog469
skaught volunteering
adiaz organization(s): Four Kitchens
andysipple organization(s): Kanopi Studios
gwvoigt organization(s): Northern Commerce
duaelfr volunteering organization(s): Happyculture
pcambra organization(s): Cambrico customer(s): Alphex Information Solutions.
edde20 volunteering
danflanagan8 organization(s): Horizontal
mbuechner
ok-steve volunteering
i-trokhanenko organization(s): Inclind Inc
wouter waeytens
scott_euser volunteering organization(s): Soapbox
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.