Contribution records
Contributors

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

Give credit to everyone
pancho pancho
droplet droplet
xanderol xanderol
jfhovinne jfhovinne
cachee cachee
rodrigoaguilera rodrigoaguilera
ofauravi ofauravi
webchick webchick
marthinal marthinal
wryz wryzam
brenda003 brenda003
pfrenssen pfrenssen
andypost andypost
tvn tvn
asirjacques asirjacques
mgifford mgifford organization(s): OpenConcept Consulting Inc.
mpv mpv
dcam dcam
lokapujya lokapujya organization(s): Babson College
David_Rothstein drothstein volunteering
le72 le72
opdavies opdavies volunteering
dqd dqd volunteering
lmeurs lmeurs
izmeez izmeez
TD44 TD44k
matt_c matt_c
drumm drumm organization(s): Drupal Association
mcdruid mcdruid organization(s): Acquia
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
g.i.joe G.I.Joe
rob.barnett hurley
stefan.r stefan.r
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.