Issue
Contribution records
Contributors

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

Give credit to everyone
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
jjgw volunteering
pameeela
lendude organization(s): iO
NitinLama volunteering organization(s): OpenSense Labs
acbramley organization(s): PreviousNext customer(s): Service NSW
abramm volunteering organization(s): DevBranch, Drupal Ukraine Community customer(s): Invotra Ltd
ayushmishra206 organization(s): OpenSense Labs
naveenvalecha volunteering
alexpott organization(s): Acro Commerce, Thunder
mohit_aghera organization(s): PreviousNext, QED42
mitthukumawat volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
ranjith_kumar_k_u organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
xjm organization(s): Agileana
ramya balasubramanian organization(s): Material customer(s): Drupal India Association
abhijith s volunteering organization(s): Zyxware Technologies
govind.maloo organization(s): Salsa Digital
Manibharathi E R organization(s): Material customer(s): Material
gaurav-mathur organization(s): Dotsquares Ltd.
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.