Contribution records
Contributors

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

Give credit to everyone
yched yched
larowlan larowlan organization(s): PreviousNext
andregp andregp organization(s): CI&T
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
yogeshmpawar yogeshmpawar organization(s): Portage CyberTech
lauriii lauriii organization(s): Acquia
phenaproxima phenaproxima organization(s): Acquia
borisson_ borisson_ organization(s): Calibrate
berdir berdir organization(s): MD Systems GmbH
smustgrave smustgrave organization(s): Mobomo
amateescu amateescu customer(s): Tag1 Consulting, Inc.
jibran jibran organization(s): Department of Customer Service, NSW
effulgentsia effulgentsia organization(s): Acquia
ashetkar ashetkar volunteering
mxr576 mxr576 volunteering organization(s): Pronovix
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
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.