Contribution records
Contributors

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

Give credit to everyone
codebymikey codebymikey organization(s): Zodiac Media
chrissnyder chrissnyder volunteering organization(s): Phase2
malcomio malcomio organization(s): Capgemini
suryabhi suryabhi
mlncn mlncn organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
rpayanm rpayanm
ibullock ibullock organization(s): Northern Commerce
doxigo doxigo volunteering organization(s): Ramsalt Lab
smustgrave smustgrave organization(s): Mobomo
edwardsay edwardsem organization(s): WebFirst, Inc.
cyu cyu organization(s): Museum of Science
greg boggs gregboggs
aron novak aronnovak organization(s): Gizra
qusai taha qusaitaha organization(s): Vardot
dburiak dburiak organization(s): ImageX
mangesh.borukar mangesh.borukar
nala-he nala-he organization(s): Museum of Science
mohammedodeh mohammedodeh
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.