Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
knalstaaf
malphas
zilverdistel
TimG1
maio1980
mindfl10
droplet
now100handed
pacome
jschrab
xjm organization(s): Acquia
ergophobe
bryancasler
staycassiopeia
tomgf
coredumperror
jacine
David_Rothstein
lionheartbf
squarecandy
deverman
katy5289
muranod
bambi_2
dianacastillo
ace11
z3cka
drupal_newb
mgifford organization(s): CivicActions
ressa
wavesailor
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
jaykandari volunteering organization(s): QED42
aiphes
gagarine volunteering
yabikami
Niklas Fiekas
danny englander
tyler.frankenstein
vinod.honey
charles belov organization(s): San Francisco Municipal Transportation Agency
indigoparadox
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.