Contribution records
Contributors

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

Give credit to everyone
jenlampton jenlampton
c4rl c4rl
koppie koppie
mbrett5062 mbrett5062
shanethehat shanethehat
socketwench rashfeather
hanpersand hanpersand
damienmckenna damienmckenna
johnshortess johnshortess
aspilicious aspilicious
drupalninja99 jaykali
thedavidmeister thedavidmeister
joelpittet joelpittet volunteering
royko_at_duo royko_at_duo
catch catch
cosmicdreams cosmicdreams
longwave longwave
aboros aboros
trevorkjorlien trevorkjorlien
vollepeer vollepeer
SebCorbin sebcorbin organization(s): Makina Corpus
lewisnyman lewisnyman
lauriii lauriii
steinmb steinmb
rainbowarray RainbowArray
akalata akalata
rteijeiro rteijeiro
mpdonadio matthew.donadio
David_Rothstein drothstein volunteering
webchick webchick organization(s): Acquia
star-szr star-szr
intergalactic overlords intergalacticoverlords
devin carlson DevinCarlson
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.