Contribution records
Contributors

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

Give credit to everyone
quicksketch quicksketch organization(s): Lullabot
waynedrupal waynedrupal
ambientdrup ambientdrup
brei9000 brei9000
z33k3r z33k3r
roball roball
vtemor vtemor
barry_fisher barry.fisher
sol1313 sol1313
ezraw ezraw
mohanprabu2 mohanprabu2
stella stella
geerlingguy geerlingguy
ellanylea ellanylea
ShannonK ShannonK
AdamFx AdamFx
yesct YesCT
ddyrr ddyrr
nicolash nicolash
gwlangie gwlangie
lefnire lefnire
dgastudio kervi
fr34ck fr34ck
nicktech nicktech
artatac artatac
sourcesoft sourcesoft
jelle_s jelles
mario002e mario002e
bkosborne bkosborne
truyenle truyenle
attiks attiks
danchadwick DanChadwick
Mark B Mark_B
aaron stanush aaronstanush
scott m. sanders scott_m.sanders
Sinan Erdem Sinan_Erdem
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.