Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
draganeror
x3cion
lewisnyman
tstoeckler
Bojhan
alexpott organization(s): Acro Commerce, Thunder
droplet
segi organization(s): Cheppers
joachim organization(s): Torchbox
joelpittet
vacho organization(s): Skilld
aleevas organization(s): Skilld
guilhermevp organization(s): CI&T
nod_ volunteering organization(s): E.voyageurs Technologies
ranjith_kumar_k_u organization(s): Zyxware Technologies
atul4drupal organization(s): Material customer(s): Drupal India Association
renatog organization(s): CI&T
ayushmishra206 organization(s): OpenSense Labs
adalbertov organization(s): CI&T
benjifisher organization(s): FRUITION
spokje
lauriii organization(s): Acquia
star-szr
jp.stacey organization(s): Magnetic Phield
David Hernández volunteering
emma.maria volunteering
manjit.singh organization(s): Material
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
saurabh-2k17 organization(s): Material customer(s): Drupal India Association
bunty badgujar organization(s): Material customer(s): Drupal India Association
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.