Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
iamEAP
ericduran
catch organization(s): Third and Grove
yurtboy
xjm volunteering organization(s): xjm
cweagans
nod_ volunteering
mikeytown2
arnested volunteering organization(s): Reload
andypost volunteering organization(s): Skilld
mherchel organization(s): Lullabot
vacho organization(s): Skilld
drup16 volunteering
grathbone volunteering
guptahemant volunteering organization(s): QED42 customer(s): Drupal India Association
jamesashok
thalles organization(s): CI&T
ayushmishra206 organization(s): OpenSense Labs
smustgrave organization(s): Mobomo
bnjmnm organization(s): Acquia
agoradesign
niklan volunteering
prudloff organization(s): Insite
jv24
tim.plunkett
ivan berezhnov volunteering organization(s): Drupal Ukraine Community customer(s): Levi9
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
rishabh vishwakarma organization(s): OpenSense Labs customer(s): DrupalFit
ambient.impact organization(s): Consensus Enterprises
anybody volunteering organization(s): DROWL.de
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.