Contribution records
Contributors

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

Give credit to everyone
johnalbin johnalbin
geerlingguy geerlingguy
stborchert stborchert
catch catch
tic2000 tic2000
webchick webchick
aspilicious aspilicious
nancydru nancyw
jensimmons jensimmons
EvanDonovan evandonovan
rfay rfay
jhodgdon jhodgdon
polishyourimage polishyourimage
davidsanger davidsanger
dantje dantje
gurtner dangswiss
danny englander danny-englander
mariusz.slonina mariusz.slonina
Adam S Adam S
Jonah Ellison jonahellison
dave reid davereid
tim.plunkett tim.plunkett
frank pfabigan phoenixseo
ineation ineation
Git commit message
Commit types
  • 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

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.