Issue
Contribution records
Contributors

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

Give credit to everyone
larowlan organization(s): PreviousNext
sakthi_dev organization(s): Specbee customer(s): Drupal India Association
daffie organization(s): Finalist
klemendev volunteering organization(s): Pylo
smustgrave organization(s): Mobomo
masipila volunteering
catch organization(s): Third and Grove
borisson_ organization(s): Calibrate
eelkeblok organization(s): iO
JvE organization(s): iO
quietone organization(s): PreviousNext
olarin organization(s): Kosada
spokje volunteering
tjtj
alexpott organization(s): Thunder
xjm organization(s): Salsa Digital
joamos volunteering
jedgar1mx volunteering
mkimmet
ivnish
brunodbo organization(s): Textillia
leeksoup
b_sharpe organization(s): ImageX
rakesh.gectcr volunteering customer(s): Stratus Meridian
aditi saraf organization(s): Valuebound customer(s): Valuebound
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.