Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
phenaproxima organization(s): Acquia
rogerpfaff organization(s): Reinblau
rosk0 organization(s): Catalyst IT
damienmckenna organization(s): Current
ranjith_kumar_k_u organization(s): Zyxware Technologies
jweowu organization(s): Catalyst IT
anybody organization(s): DROWL.de
xurizaemon volunteering organization(s): Catalyst IT
smustgrave organization(s): Mobomo
grevil volunteering organization(s): DROWL.de
recrit organization(s): Phase2
amanp organization(s): Catalyst IT
shalini_jha organization(s): QED42 customer(s): QED42
martijn de wit organization(s): Ablerz
kristen pol organization(s): QuantCDN, Salsa Digital
pooja saraah organization(s): Material customer(s): Drupal India Association
prem suthar organization(s): Material customer(s): Drupal India Association
thomas.frobieter organization(s): DROWL.de
loze
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.