Issue
Contribution records
Contributors

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

Give credit to everyone
lobsterr
nsciacca
ghalenir
felipe38113
xlith
logickal organization(s): The Weather Company
redzeuf organization(s): Happy Coding
jweirather
svenryen organization(s): Ramsalt Lab
maxplus
mrpauldriver
digitalcatalyst
mably
mgifford organization(s): OpenConcept Consulting Inc.
nkoporec volunteering organization(s): Agiledrop - Your Trusted Drupal Teammates
swirt organization(s): CivicActions customer(s): Department of Veterans Affairs
superkhaliloo
oriol_e9g organization(s): Diputació de Barcelona
shaung75
cedewey volunteering organization(s): DevCollaborative, LLC
nickdickinsonwilde volunteering organization(s): Taoti Creative
ñull volunteering
jigish.addweb organization(s): AddWeb Solution Pvt. Ltd.
d.clarke
ahmad abbad volunteering
Mike.Brawley
stefan.korn organization(s): Stefan Korn - Webentwicklung
dd 85
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.