Issue
Contribution records
Contributors

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

Give credit to everyone
dqd
jonathanmd
moniuch
tsvenson
torotil
swentel
jasperknops
macmladen
circuscowboy
mgifford
capellic
guictx
johnpitcairn
bcobin
jwilson3
lawik
designguru
nicholsonma
lavastein
yesct
cb
gaele
olliebourne
schen
luksak
Homotechsual
dmatamales
7wonders
thekevinday
chrismacnaughton
greenskin
awolfey organization(s): Capellic LLC
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
sirko_el volunteering
seorusus
l0ke organization(s): JAKALA (formerly FFW) customer(s): JAKALA (formerly FFW)
Marc-Antoine
dave reid
frank ralf
alexander.sibert
Johann Wagner
joseph.olstad
chris matthews volunteering
james feng
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.