Contribution records
Contributors

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

Give credit to everyone
bobbers bobbers
derrie derrie
meanbeth meanbeth
sketchysteven sketchysteven
mayobutter mayobutter
mp165 mp165
escapeit escapeit
cdracars cdracars
kettari kettari
mikeryan mikeryan
jackread jackread
dollar_dad dollar_dad
karens karens
xenyo xenyo
stinky stinky
fossle fossle
rwilson0429 rwilson0429
karunadave karunadave
gdbassett gdbassett
yowzer yowzer
jennypanighetti jennypanighetti
WoozyDuck WoozyDuck
jerdavis jerdavis
kenwest kenwest
zorax zorax
PBenz PBenz
shabam shabam
ressa ressa
helgew helgew
dags davidjdagino
jkingsnorth JKingsnorth
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.