Contribution records
Contributors

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

Give credit to everyone
cilefen cilefen
anchal29 anchal29 volunteering
rbordallo rbordallo organization(s): ASPgems
betarobot betarobot
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
aerozeppelin aerozeppelin
gvso gvso
alvar0hurtad0 alvar0hurtad0 organization(s): ASPgems
joyceg joyceg
martin107 martin107
istryker istryker
almaudoh almaudoh
peacog Peacog volunteering
sebas5384 sebas5384 volunteering
chgasparoto chgasparoto volunteering organization(s): CI&T
erickbj erickbj organization(s): CI&T
xjm xjm organization(s): Acquia
rodrigoac rodrigoac organization(s): CI&T
star-szr star-szr volunteering organization(s): Northern Commerce
wim leers wimleers organization(s): Acquia
claudiu.cristea claudiucristea organization(s): Webikon
sagar ramgade SagarRamgade volunteering organization(s): Trigyn Technologies Ltd
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.