Issue
Contribution records
Contributors

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

Give credit to everyone
ckrina organization(s): Lullabot
lauriii organization(s): Acquia
reinchek volunteering organization(s): Hinto Group
naresh_bavaskar volunteering organization(s): QED42
sibustephen volunteering
kishor_kolekar volunteering organization(s): QED42
akashkumar07
jordanwood organization(s): Northern Commerce
hotwebmatter volunteering
KondratievaS organization(s): Skilld
kostyashupenko organization(s): Skilld
sauravk volunteering organization(s): Material customer(s): Drupal India Association
shaktik volunteering organization(s): Material customer(s): Drupal India Association
bhumikavarshney volunteering organization(s): OpenSense Labs
xjm organization(s): Acquia
nitesh624 volunteering organization(s): Material customer(s): Drupal India Association
atul4drupal organization(s): Material
vinodhini.e organization(s): UniMity Solutions Pvt Limited
ravi.shankar organization(s): OpenSense Labs
szalapski.adam@gmail.com organization(s): Pegasystems
krzysztof domański organization(s): abventor
neslee canil pinto organization(s): Specbee
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.