Contribution records
Contributors

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

Give credit to everyone
pyrello pyrello
TerrenceLP TerrenceLP
alexis alexis
Coyote coyote
prosequent prosequent
amitkarpe amitkarpe
gordon gordon
sime sime
pbhalesain pbhalesain
Coop1979 Coop1979
BullCreek BullCreek
schavester schavester
rszrama rszrama
BioALIEN BioALIEN
wgknowles wgknowles
rickvug rickvug
kenyob kenyob
jbeall jbeall
summit summit
randomuser randomuser
halfelven halfelven
WisTex WisTex
brmassa brmassa
cayenne cayenne
robloach robloach
rjleigh rjleigh
budda budda
a319903 a319903
artatac artatac
senthiln senthiln
mfb mfb
scottrigby scottrigby
apb1991 apb1991
awilliams awilliams
MPDano MPDano
dublin drupaller jasonm3m
Walt Esquivel Walt_Esquivel
matt@antinomia antinomia
as medias@asmedias.net as_medias-at-asmedias.net
lunk rat LunkRat
Keith Hurst Keith_Hurst
yngens snegny
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.