Contribution records
Contributors

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

Give credit to everyone
afsch alexito volunteering organization(s): Lullabot customer(s): State of Georgia
hhvardan hhvardan organization(s): Last Call Media
jrochate jrochate
rajeshreeputra Rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc.
saidatom saidatom organization(s): Squarebit
xjm xjm organization(s): Agileana
dimilias dimilias customer(s): European Commission and European Union Institutions, Agencies and Bodies
bhanu951 Bhanu951 volunteering
deepakkm deepakkm
smustgrave smustgrave organization(s): Mobomo
alexpott alexpott organization(s): Acro Commerce, Thunder
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
larowlan larowlan organization(s): PreviousNext
jmester13 jmester13 volunteering
prem suthar PremSuthar organization(s): Material customer(s): Drupal India Association
akram khan Akramkhan786 volunteering organization(s): Material customer(s): Drupal India Association
claudiu.cristea claudiucristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
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.