Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jibran
Mixologic organization(s): Drupal Association
donquixote
larowlan
phenaproxima organization(s): Acquia
alexpott organization(s): Thunder
pingwin4eg volunteering
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
mglaman organization(s): Centarro
mparker17 volunteering
cmcintosh organization(s): Wembassy llc customer(s): Wembassy llc
kingdutch organization(s): Open Social
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): Drupal Association, European Commission and European Union Institutions, Agencies and Bodies
rainbowarray organization(s): Lullabot
mikelutz volunteering organization(s): ICON Interactive
catch organization(s): Tag1 Consulting, Inc. customer(s): Drupal Association
mondrake volunteering
mile23 volunteering
rodrigoaguilera organization(s): Upstreamable
xjm volunteering organization(s): xjm
tedbow organization(s): Acquia
grasmash
pandaski organization(s): govCMS (Australian Government Department of Finance)
shaal volunteering organization(s): Palantir.net, Phase2 customer(s): Tableau
dww volunteering
stefaniev
pasqualle volunteering
grimreaper organization(s): Smile
kim.pepper organization(s): PreviousNext
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
shubham.prakash organization(s): OpenSense Labs
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.