Contribution records
Contributors

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

Give credit to everyone
danchadwick DanChadwick
atul_ghate atulghate
quietone quietone organization(s): PreviousNext
zaryab_drupal zaryab_drupal organization(s): OpenSense Labs customer(s): DrupalFit
mcdruid mcdruid organization(s): Acquia
robloach robloach organization(s): Kalamuna
wylbur wylbur organization(s): Electric Citizen
benjifisher benjifisher volunteering
catch catch organization(s): Third and Grove
cilefen cilefen
damienmckenna damienmckenna organization(s): Third and Grove
greggles greggles organization(s): Colorado Governor's Office of Information Technology - Colorado Digital Service
kristiaanvandeneynde kristiaanvandeneynde organization(s): Factorial.io
longwave longwave organization(s): Full Fat Things customer(s): Acquia
poker10 poker10 organization(s): ActivIT s.r.o.
zengenuity zengenuity organization(s): Zengenuity / DrupalTutor
larowlan larowlan organization(s): PreviousNext
w01f W01F
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.