Issue
Contribution records
Contributors

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

Give credit to everyone
jeremy
Bevan
peterx
jstoller
BenK
likewhoa
didiercastelnau
Anticosti
sergebw
joostvdl
RandalK
chriz001
oscardax
coolhandlukek2
cwightrun
wolfmarter
ap500
shadowmihai
ParisLiakos
mrharolda
sorensong
perandre
aaronortega
MtRoxx
halloffame
berreyst
Vinnie1991
joshmccormack
basvredeling
mstrelan
cajmcmahon
thomjjames
tempo22
mrpauldriver
mikeprinsloo
cesareaugusto
juliakoelsch
BeaPower
franzkewd
BazzeFTW
andrew_mallis
damiandab
sethfisher
jboese
jenlampton
forexpivots
rockylhc
mgifford
dgastudio
mathankumarc
tchopshop
delibob
davidgenetic
dfletcher volunteering
galooph organization(s): Code Enigma
anybody volunteering organization(s): DROWL.de
Alex Andrascu
AdrianC-1
ryan osītis
josh waihi
Stefan Haas
edward.kay
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.