Contribution records
Contributors

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

Give credit to everyone
vood002 jpez
kirkkala kirkkala volunteering organization(s): Mearra (formerly known as Wunder)
brankoc brankoc volunteering
MrMason MrMason organization(s): Sealed Air
alexpott alexpott organization(s): Acro Commerce, Thunder
seanb seanB organization(s): Acquia
phenaproxima phenaproxima organization(s): Acquia
pameeela pameeela
b_sharpe b_sharpe organization(s): ImageX
kekkis kekkis organization(s): Exove
dshumaker dshumaker organization(s): Phase2
gargsuchi gargsuchi volunteering
vacho vacho organization(s): Skilld
marcoscano marcoscano organization(s): Lullabot customer(s): New Relic
almunnings almunnings
lunk rat LunkRat
joshua.boltz joshua.boltz organization(s): Current
ilya.no ilya_no volunteering organization(s): Skilld customer(s): Skilld
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.