Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jeffdavidgordon
sylus
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
logickal organization(s): The Weather Company
rosk0 organization(s): Catalyst IT
aneek volunteering
gold organization(s): Catalyst IT
mradcliffe organization(s): Kosada
jakegibs617 volunteering
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
cilefen
smustgrave organization(s): Mobomo
smarchese
abelass
saadaouiyos
elimw
dydave organization(s): Code Enigma
vistree
andypost volunteering organization(s): Skilld
ravi.shankar organization(s): OpenSense Labs
andrew.wang organization(s): Ontario Digital Service
m.stenta organization(s): Farmier
liam morland volunteering organization(s): OpenPlus, Scouting Waterloo Region
mondrake volunteering
ironnuts volunteering
oulalahakabu
dan3h
jmcerda volunteering organization(s): Wilkes & Liberty
quietone organization(s): PreviousNext
daffie organization(s): Finalist
phpsubbarao
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.