Contribution records
Contributors

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

Give credit to everyone
britter britter
jhodgdon jhodgdon
cilefen cilefen
daften daften organization(s): District09
colan colan organization(s): Colan Schwartz Consulting
memtkmcc memtkmcc organization(s): Omega8.cc
catch catch organization(s): Third and Grove
xjm xjm organization(s): Acquia
wesleydv wesleydv
fago fago organization(s): drunomics
Munavijayalakshmi munavijayalakshmi organization(s): Valuebound
benjifisher benjifisher organization(s): Isovera
osopolar osopolar
philnguyen philnguyen volunteering
dagmar dagmar
xlin xq1003 volunteering
tomogden tomogden
robertloo robertloo
dhopki12 dhopki12
yesct YesCT
lauriii lauriii organization(s): Druid
chera.jaswinder chera.jaswinder
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.