Contribution records
Draft
Contributors

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

Give credit to everyone
bojanz bojanz organization(s): Centarro
vijaycs85 vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
tacituseu tacituseu
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
vsujeetkumar vsujeetkumar organization(s): Material customer(s): Drupal India Association
manojithape manojithape organization(s): QED42 customer(s): Drupal India Association
kartagis Kartagis volunteering
mile23 Mile23 volunteering
quietone quietone volunteering
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
lauriii lauriii organization(s): Acquia
bnjmnm bnjmnm organization(s): Acquia
hooroomoo hooroomoo organization(s): Acquia
smustgrave smustgrave organization(s): Mobomo
narendrar NarendraR volunteering organization(s): Acquia
benjifisher benjifisher organization(s): Tag1 Consulting, Inc.
manuel garcia manuelgarcia volunteering organization(s): Appnovation
bs pavan BSPavan organization(s): Material
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.