Contribution records
Contributors

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

Give credit to everyone
shabbir Shabbir organization(s): Trigyn Technologies Ltd
heikki heikki organization(s): Avoltus Oy
benjifisher benjifisher organization(s): Isovera
Madis dooshta volunteering organization(s): ADM Interactive
brahmjeet789 brahmjeet789 volunteering organization(s): gai Technologies Pvt Ltd
di3gopa di3gopa customer(s): Rootstack
fonant Fonant
vacho vacho organization(s): Skilld
asrob asrob organization(s): Integral Vision Ltd
jts86 joel-travieso organization(s): Four Kitchens
idebr idebr organization(s): ezCompany, iO
lendude Lendude volunteering organization(s): ezCompany, iO
aiphes aiphes
dww dww volunteering
alexpott alexpott organization(s): Acro Commerce, Thunder
acbramley acbramley organization(s): PreviousNext
aadesh.verma aadeshverma
joshua.boltz joshua.boltz organization(s): Current
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.