Contribution records
Contributors

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

Give credit to everyone
dpi dpi organization(s): PreviousNext
arnested arnested organization(s): Reload
quietone quietone organization(s): PreviousNext
mondrake mondrake volunteering
longwave longwave organization(s): Full Fat Things
smustgrave smustgrave organization(s): Mobomo
mstrelan mstrelan organization(s): PreviousNext
larowlan larowlan organization(s): PreviousNext
mortona2k mortona2k volunteering
dydave DYdave organization(s): Code Enigma
shalini_jha shalini_jha organization(s): QED42 customer(s): QED42
danielveza DanielVeza volunteering organization(s): PreviousNext
znerol znerol
acbramley acbramley organization(s): PreviousNext
mxh hauptm
elc elc
alexpott alexpott organization(s): Acro Commerce, Thunder
nicxvan nicxvan organization(s): nLightened Development LLC
m.stenta mstenta
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.