Contribution records
Contributors

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

Give credit to everyone
alex_b alexb
budda budda
patcon patcon
Bevan bevan
Holoduke Holoduke
EmanueleQuinto EmanueleQuinto
sbydrupal sbydrupal
dfgcvb dfgcvb
farhadhf farhadhf
mareks mareks
kscheirer kscheirer
xiahy xiahy
ufku ufku
Rob_Feature bobchristenson
twistor twistor
senzaesclusiva senzaesclusiva
reszli reszli
megachriz megachriz volunteering
paulsheldrake paulsheldrake
dshields dshields organization(s): Canadian Blood Services
geoffreyr geoffreyr
dhigby dhigby
Arts and Ideas Arts and Ideas
subu.purohit subu.purohit
mr.york york
giomax giomax
bluegeek9 bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
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.