Contribution records
Contributors

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

Give credit to everyone
nathancz nathancz
cilefen cilefen volunteering organization(s): Institute for Advanced Study
markdorison markdorison organization(s): Chromatic
borisson_ borisson_ volunteering
tstoeckler tstoeckler organization(s): bio.logis Genetic Information Management GmbH
ndobromirov ndobromirov organization(s): JAKALA (formerly FFW)
danielveza DanielVeza organization(s): PreviousNext
meeni_dhobale meeni_dhobale
mayurgajar mayurgajar
kapilv kapilkumar0324
samitk samit.310
xjm xjm organization(s): Zoocha, xjm, QED42
moshe weitzman weitzman
nicxvan nicxvan organization(s): nLightened Development LLC
phenaproxima phenaproxima organization(s): Acquia
kristiaanvandeneynde kristiaanvandeneynde organization(s): Tag1 Consulting, Inc.
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.