Issue
Contribution records
Contributors

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

Give credit to everyone
pranit84 volunteering
thalles organization(s): CI&T
berdir organization(s): MD Systems GmbH
andreyjan organization(s): JAKALA (formerly FFW)
neelam_wadhwani organization(s): Valuebound customer(s): Valuebound
shobhit_juyal
jcnventura organization(s): 1xINTERNET
komalk organization(s): Material customer(s): Drupal India Association
japerry organization(s): Acquia
naveenvalecha volunteering
damienmckenna organization(s): Current
kristen pol organization(s): Hook 42
sahana _n organization(s): Specbee
chr.fritsch organization(s): Thunder
lisa.rae volunteering organization(s): Interpersonal Frequency
kim.pepper
chris matthews
e.bogatyrev volunteering organization(s): EPAM
hass
Git commit message
Commit types
  • 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

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.