Contribution records
Contributors

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

Give credit to everyone
paranojik paranojik organization(s): Cando
LittleRedHen LittleRedHen
catch catch
yonailo yonailo
davewilly davewilly volunteering
lstirk lstirk
jfalkner jonathanfalkner volunteering organization(s): Phase2
smustgrave smustgrave
kwfinken kwfinken organization(s): Michigan State University customer(s): Michigan State University
maximpodorov maximpodorov
deciphered deciphered volunteering
damienmckenna damienmckenna organization(s): Current
thomwilhelm ThomWilhelm
bsains bsains
dsnopek dsnopek
cboyden cboyden
broon broon
jcorrao jcorrao
gdaw gdaw volunteering
brayfe brayfe
mrgoodfellow mrgoodfellow
tessa bakker TessaBakker organization(s): ezCompany
das-peter daspeter organization(s): Cando
sri@re sri@re
stefan.r stefan.r
joseph.olstad joseph.olstad
kc-drupal anutoshg volunteering
hass hass
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.