Contribution records
Contributors

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

Give credit to everyone
stella stella
mrfelton mrfelton
tekante tekante
YK85 YK85
phreestilr phreestilr
pcave pcave
jaybee1001 jaybee1001
AlexisWilke alexiswilke
MadtownLems MadtownLems
jmuessig jmuessig
levelos levelos
johnthomas00 johnthomas00
neilnz neilnz
Fortyhands Fortyhands
dannypfeiffer dPfeiffer
kenwest kenwest
bcmiller0 bcmiller0
sreynen sreynen
dbassendine dbassendine
drupalsteve drupalsteve
chicodasilva chicodasilva
Reevescorp Reevescorp
jrust jrust
adr_p adr_p
grendzy grendzy
mstrelan mstrelan
yub_yub yub_yub
msumme msumme
shaisachs shaisachs
seanr seanr
rickbydesign rickbydesign
shaundychko ShaunDychko
wiherek wiherek5
tomswiggers tomswiggers
phil_esq. phil_esq.
robert castelo robert-castelo
ngmaloney ngmaloney
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.