Contribution records
Contributors

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

Give credit to everyone
larowlan larowlan
podarok podarok
c4rl c4rl
catch catch
berdir berdir
jenlampton jenlampton
mbrett5062 mbrett5062
steveoliver steveoliver
eigentor eigentor
webchick webchick
GeminiAgaloos g3m1n1
thedavidmeister thedavidmeister
joelpittet joelpittet volunteering
ressa ressa
carsonblack carsonblack
fabianx Fabianx volunteering
jwilson3 jwilson3
yesct YesCT
cosmicdreams cosmicdreams
geoffreyr geoffreyr
johannez johannez
jhodgdon jhodgdon
mgifford mgifford
jerdavis jerdavis
markhalliwell markcarver
naveenvalecha naveenvalecha
drupalmonkey drupalmonkey
gapple gapple
mikl mikl
klonos klonos
akalata akalata
steinmb steinmb
xjm xjm
star-szr star-szr organization(s): Northern Commerce
sean charles SeanCharles
les lim lesmana
manuel garcia manuelgarcia
a-fro a-fro
stefan.r stefan.r
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.