Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
bnjmnm organization(s): Acquia
lauriii organization(s): Acquia
catch organization(s): Third and Grove
xjm organization(s): Acquia, xjm
zrpnr organization(s): Acquia
aaronmchale
nod_ volunteering organization(s): Acquia, Smile
rajandro volunteering organization(s): Material customer(s): Drupal India Association
droplet
saschaeggi organization(s): Unic
andrewmacpherson volunteering
kapilv volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
bserem organization(s): zehnplus
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
jonathanshaw
artusamak
andypost volunteering organization(s): Skilld
rikki_iki organization(s): PreviousNext
NIKS_Artreaktor
effulgentsia organization(s): Acquia
mgifford organization(s): CivicActions
quietone organization(s): PreviousNext
chi
pameeela organization(s): Technocrat
wim leers organization(s): Acquia
ghost of drupal past
kim.pepper organization(s): PreviousNext
tim.plunkett organization(s): Acquia
kentr volunteering
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.