Contribution records
Draft
Contributors

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

Give credit to everyone
alex_b alexb
boombatower boombatower
yhahn yhahn
adrian adrian
febbraro febbraro
arianek arianek
langworthy langworthy
jgraham jgraham
jhedstrom jhedstrom
eaton eaton
chrisshattuck chrisshattuck
dixon_ dixon
Jackinloadup Jackinloadup
sun sun
bonobo bonobo
webchick webchick
chx chx
David_Rothstein drothstein
EvanDonovan evandonovan
dasjo dasjo
ademarco ademarco
tstoeckler tstoeckler
jrbeeman jrbeeman
catch catch
amateescu amateescu
hefox hefox
favrik favrik
s_leu s_leu
mpotter mpotter
berdir berdir
mitokens mitokens volunteering
wizonesolutions wizonesolutions volunteering
misc mikkeX organization(s): Mearra (formerly known as Wunder)
andrewbelcher andrewbelcher organization(s): FreelyGive
quietone quietone volunteering
boris mann borismann
jason.fisher jason.fisher
moshe weitzman weitzman
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.