Contribution records
Draft
Contributors

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

Give credit to everyone
tignux tignux
sonicthoughts sonicthoughts
iAutom8 iAutom8
Taxoman Taxoman
jefdrupal jefdrupal
ngstigator ngstigator
antiqel antiqel
particlegirl particlegirl
Oceanman Oceanman
mailking mailking
SeanBannister seanbannister
likewhoa likewhoa
petercasier petercasier
LBen LBen
rovo rob_dean
avantcontra avantcontra
FluxRostrum FluxRostrum
infojunkie kratib
joomlerrostov hahaconda
rvm88 rvm88
mxmilkiib milkmiruku
vskipper vskipper
mikemadison lalweil
batje batje
memoday memoday
my06 my06
niccolox niccolo
cweagans cweagans
omega8cc omega8cc
geerlingguy geerlingguy
Jotnarta Jotnarta
andrew_mallis Andrew_Mallis
greenskunk GreenSkunk volunteering
robin monks robinmonks
jason ruyle jasonruyle
milos.kroulik milos.kroulik
martin.l martin.l
finedesign finedesign
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.