Issue
Contribution records
Contributors

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

Give credit to everyone
catch organization(s): Third and Grove
spokje volunteering
longwave organization(s): Full Fat Things
joelpittet organization(s): The University of British Columbia
cmlara
szato organization(s): Brainsum customer(s): Novozymes A/S
jrearick organization(s): Principal Financial Group
timwood
eric_a organization(s): Dutch Open Projects, RIVM
effulgentsia organization(s): Acquia
dww volunteering
alexpott organization(s): Acro Commerce, Thunder
stevenpatz volunteering
Monster971
berdir organization(s): MD Systems GmbH
arne_hortell
Carsten
dave reid volunteering organization(s): Lullabot customer(s): Principal Financial Group
Mohmed Fasil Paleri
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.