Contribution records
Contributors

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

Give credit to everyone
bfroehle bfroehle
chx chx
rfay rfay
babbage babbage
ralphb ralphb
mrsinguyen mrsinguyen
verta verta
pillarsdotnet pillarsdotnet
marcvangend marcvangend
geerlingguy geerlingguy
wOOge wooge
daglees jdaglees
twowheeler twowheeler
dadaisme dadaisme
gamgllc gamgllc
hkirsman hkirsman
gfury gfury
uotonyh uotonyh
jvieille jvieille
MatthijsG MatthijsG volunteering
LynnS lynns
robcarr robcarr
Collins405 chriscollins405
aramboyajyan topsitemakers
markdc markdc
bradallenfisher baf139
designcrs designcrs
ñull com2
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.