Issue
Contribution records
Contributors

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

Give credit to everyone
hablutzel1
matthijs
filsterjisah customer(s): District09
David_Rothstein
DnaX
dcam
nod_ organization(s): Smile
Jalandhar
mgifford organization(s): OpenConcept Consulting Inc.
jhedstrom
anybody
MathieuMa
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
geertvd organization(s): Geert van Dort, XIO
droplet
peterpoe volunteering
catch organization(s): Third and Grove
ufku
smaz organization(s): Five Mile Media
Jeroen_005 organization(s): Pàu customer(s): District09
maacl
wesleydv organization(s): District09
miroslavbanov volunteering organization(s): JAKALA (formerly FFW)
aleevas organization(s): Skilld
mpp organization(s): AmeXio Fuse customer(s): District09
GrandmaGlassesRopeMan organization(s): DocuSign
alexj12 volunteering organization(s): Zoocha
mrinalini9 organization(s): Material customer(s): Drupal India Association
jeroent organization(s): iO
spencer95@gmail.com organization(s): S8080
star-szr organization(s): Northern Commerce
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.