Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
samhassell
joachim organization(s): Factorial.io
jhodgdon
mile23 volunteering
heddn organization(s): MTech, LLC
alvar0hurtad0 organization(s): ASPgems
marabak organization(s): Lumini
JulienD volunteering
opdavies organization(s): Investis Digital
metzlerd
colan organization(s): Colan Schwartz Consulting
mradcliffe organization(s): Kosada
quietone volunteering organization(s): PreviousNext
karishmaamin organization(s): Specbee
pradhumanjain2311 organization(s): OpenSense Labs customer(s): DrupalFit
anchal_gupta organization(s): Material customer(s): Drupal India Association
imclean organization(s): Digital Ink
smustgrave organization(s): Mobomo
shubham chandra volunteering organization(s): Dotsquares Ltd.
Ankit.Gupta organization(s): Dotsquares Ltd.
gaurav-mathur organization(s): Dotsquares Ltd.
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.