Contribution records
Contributors

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

Give credit to everyone
ultimike ultimike organization(s): DrupalEasy
damienmckenna damienmckenna organization(s): Current
kthull kthull
gdemet gdemet organization(s): Palantir.net
rainbowarray RainbowArray organization(s): Lullabot
nickdickinsonwilde NickDickinsonWilde volunteering organization(s): BriarMoon Design
mherchel mherchel organization(s): Lullabot
rachel_norfolk rachel_norfolk organization(s): Drupal Association
cmcintosh cmcintosh
drnikki drnikki volunteering organization(s): Kanopi Studios
nerdstein nerdstein volunteering organization(s): Hook 42
davidhernandez davidhernandez volunteering
kclarkson kclarkson organization(s): Drupal Diversity & Inclusion
rubyji rubyji volunteering
lslinnet lslinnet volunteering
catch catch volunteering
gapple gapple volunteering
weekbeforenext weekbeforenext volunteering
jenlampton jenlampton organization(s): Jeneration Web Development
zsofi.major zsofi.major volunteering
alex ua alexua
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.