Contribution records
Contributors

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

Give credit to everyone
David_Rothstein drothstein volunteering
metallized sergiomeneses
pianomansam pianomansam
klausi klausi
kurkuma kurkuma volunteering
yesct YesCT
btopro btopro
ashepherd ashepherd
mallezie mallezie
dgtlmoon dgtlmoon
iamEAP iamEAP organization(s): Tableau
lokapujya lokapujya organization(s): Babson College
guardiola86 guardiola86
roynilanjan roynilanjan
chriscode chriscode
jgrubb jgrubb
thedut thedut
garyebickford garyebickford volunteering
fago fago organization(s): drunomics
MrSchoolcraft majorhallux volunteering
ngiann ngiann
klokie klokie volunteering
4aficiona2 4aficiona2
stefan.r stefan.r
Koen.Pasman Koen.Pasman organization(s): Aubergine IT
joseph.olstad joseph.olstad volunteering
mariano.barcia mariano.barcia organization(s): ASM Web Services S.L.
jaskaran.nagra jaskaran.nagra
shane birley shanebirley volunteering
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.