Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
benjaminbradley organization(s): Polycot Associates customer(s): Autodesk Knowledge Network
drupgirl
kclarkson
markdc
berdir organization(s): MD Systems GmbH
catch organization(s): Third and Grove
webel
dercheffe
ptmkenny
liliplanet
mohit_aghera organization(s): PreviousNext, QED42
larowlan organization(s): PreviousNext
vikashsoni volunteering organization(s): Zyxware Technologies
segovia94 volunteering
quietone volunteering
rclemings
aaronbauman organization(s): Message Agency
benjifisher volunteering organization(s): FRUITION
rossidrup
simohell
iancawthorne
sajithathukorala volunteering
prabha1997 organization(s): QED42 customer(s): QED42
shawn dearmond
knyshuk.vova organization(s): Drupal Ukraine Community, Internetdevels
gaurav.kapoor organization(s): Axelerant, werk21 customer(s): Drupal India Association
edward.peters
shabana.navas
prashant.c volunteering organization(s): QED42 customer(s): QED42
hitchshock volunteering organization(s): DevBranch, Drupal Ukraine Community, Dropsolid
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.