Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jhodgdon
larowlan organization(s): PreviousNext
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
johnwebdev
chi
dww volunteering
webchick organization(s): Acquia
ressa organization(s): Ardea
aaronmchale organization(s): The University of Edinburgh
dawehner volunteering
andypost volunteering organization(s): Skilld
mile23 volunteering organization(s): CivicActions
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): Drupal Association, European Commission and European Union Institutions, Agencies and Bodies
mradcliffe organization(s): Kosada
rfay organization(s): DDEV
douggreen volunteering
geerlingguy
yoroy organization(s): Roy Scholten
frob organization(s): Clarity Innovations, Inc.
eelkeblok organization(s): iO
jaypan
solideogloria
xjm volunteering organization(s): xjm
catch organization(s): Third and Grove
neclimdul volunteering
joachim volunteering
greg.1.anderson organization(s): Pantheon
norman.lol organization(s): 1xINTERNET
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.