Contribution records
Contributors

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

Give credit to everyone
walkero walkero
interlated interlated volunteering
vpa24 vpa24 volunteering
tyler36 tyler36 organization(s): Inter Quest Co.,Ltd.
olarin Olarin organization(s): Kosada
cesarg cesarg
rclemings rclemings
mayankguptadotcom mayankguptadotcom volunteering
jerrac jerrac
geerlingguy geerlingguy organization(s): Midwestern Mac, LLC
tilottama11 tilottama_ojha
opdavies opdavies volunteering
bisonbleu bisonbleu
mxr10_ mxr10_
lennart lennart
jonathan_hunt jonathanhunt volunteering
pacproduct pacproduct organization(s): Makina Corpus
megachriz megachriz organization(s): WebCoo
ambient.impact Ambient.Impact organization(s): Consensus Enterprises
chris burge ChrisBurge volunteering
dan kolbas dkolbas
dotpex dotpex
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.