Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
yched
carwin
donSchoe
bfroehle
steinmb
betoscopio
chi
Yuri
noeldbs
chx
xjm
Zgear
BrockBoland
domidc
aspilicious
catch
marthinal
kotnik
warmth
pfrenssen
rlmumford
bailey86
IRuslan
grisendo
TheTomatoFarmerReturns
nDigitHQ
xjkwak
meysamm
hgoto volunteering
dagmar organization(s): Globant
diaspar
ahughes3 volunteering
rootwork
_Archy_ organization(s): PitechPlus
vsujeetkumar organization(s): Material customer(s): Drupal India Association
daffie
quietone volunteering
golddragon007 organization(s): European Commission and European Union Institutions, Agencies and Bodies, Petend
dinazaur volunteering organization(s): DevBranch
lunk rat
mahesh.umarane
ion.macaria volunteering
olafveerman
anybody volunteering organization(s): DROWL.de
tstoeckler organization(s): resc.
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.