Contribution records
Contributors

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

Give credit to everyone
mradcliffe mradcliffe organization(s): Kosada
Soundvessel Soundvessel
chi Chi
jrockowitz jrockowitz volunteering organization(s): The Big Blue House
hickok hickok
malcomio malcomio organization(s): Capgemini
pancho pancho volunteering
mrweiner mrweiner volunteering organization(s): Flat 9
pameeela pameeela
djdevin devin organization(s): Cadmium
bnjmnm bnjmnm organization(s): Acquia
utkarsh_33 Utkarsh_33 organization(s): Acquia
lauriii lauriii organization(s): Acquia
joachim joachim volunteering
smustgrave smustgrave organization(s): Mobomo
catch catch organization(s): Third and Grove
hooroomoo hooroomoo organization(s): Acquia
anybody Anybody volunteering organization(s): DROWL.de
longwave longwave organization(s): Full Fat Things
alan d. aland
tim.plunkett tim.plunkett organization(s): Acquia
wim leers wimleers organization(s): Acquia
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.