Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
greggles
aalapati
LarsKramer
marthinal
penyaskito
kfritsche
hefox
Grayside
mgifford
alansaviolobo
rpayanm
oakulm volunteering
ivrh
cilefen
dpi volunteering organization(s): PreviousNext
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
darvanen
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
mxr576 organization(s): Pronovix
dave reid
damien tournoud
ivansb@drupal.org
mr.baileys
hitesh-jain volunteering organization(s): Acquia
prudloff organization(s): Insite
smustgrave organization(s): Mobomo
gaëlg organization(s): Insite
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.