Contribution records
Contributors

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

Give credit to everyone
merlinofchaos merlinofchaos
gbilling gbilling
frankcarey frankcarey
milksamsa milksamsa
ChrisBryant chrisbryant
dkruglyak dkruglyak
nco71 nco71
cgjohnson cgjohnson
mrfelton mrfelton
LEternity LEternity
pribeh pribeh
crea crea
colin_young colin_young
ppcc ppcc
Nestor Nestor
pankaj01 pankaj01
g76 g76
ryanrain ryanrain
thrash632 thrash632
hutch120 hutch120
mtpultz mtpultz
tugis tugis
mazdakaps mazdakaps
goatsee goatsee
director87 director87
geosmaga geosmaga
Countzero Countzero
drupalok drupalok
mirie mirie
flavio_tito flavio_tito
aaronelborg AaronELBorg
neRok neRok
drupalye drupalye
cyberzeus cyberzeus
japerry japerry organization(s): Drupal Association
Parkes Design ParkesDesign
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.