Issue
Contribution records
Contributors

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

Give credit to everyone
pendashteh
aaronbauman
mahtoranjeet
dawehner volunteering organization(s): Tag1 Consulting, Inc.
amaisano
David_Rothstein volunteering
gambry organization(s): EPAM
chrisgross
amit0212 volunteering organization(s): Iksula
altrugon organization(s): Affinity Bridge
raphaeltbm
mlncn organization(s): Agaric customer(s): Drutopia, National Institute for Children's Health Quality
vj volunteering
aiphes
dieterholvoet volunteering organization(s): Minsky
quietone organization(s): PreviousNext
ranjith_kumar_k_u organization(s): Zyxware Technologies
damienmckenna organization(s): Current
smustgrave organization(s): Mobomo
rodrigoaguilera organization(s): Ymbra customer(s): Ymbra
neclimdul volunteering
anruether organization(s): Geeks4Change
amateescu customer(s): Tag1 Consulting, Inc.
tim.plunkett
joachim organization(s): Gulp Digital
catch organization(s): Third and Grove
phenaproxima organization(s): Acquia
godotislate volunteering
mstrelan
alexpott organization(s): Acro Commerce, Thunder
longwave organization(s): Full Fat Things
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.