Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
ckrina organization(s): Lullabot
pzajacz organization(s): Brainsum customer(s): Tieto
saschaeggi organization(s): Unic
fhaeberle organization(s): bitegra Solutions, PARAGON Executive Services GmbH
katannshaw organization(s): Lullabot
huzooka organization(s): Cheppers customer(s): Acquia
martin107 volunteering
berdir organization(s): MD Systems GmbH
bnjmnm organization(s): Acquia
lauriii organization(s): Acquia
katherined
andypost volunteering organization(s): Skilld
tanubansal organization(s): Salsa Digital
volkswagenchick organization(s): Kanopi Studios
gauravvvv organization(s): Material, OpenSense Labs customer(s): Drupal India Association
stefdewa organization(s): Calibrate
miro_dietiker organization(s): MD Systems GmbH
mgifford organization(s): CivicActions
finnsky organization(s): Skilld
tim.plunkett organization(s): Acquia
sakthivel m organization(s): QED42 customer(s): Drupal India Association
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
charles belov organization(s): San Francisco Municipal Transportation Agency
quietone organization(s): PreviousNext
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.