Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
stevekeiretsu volunteering
scotwith1t
pancho volunteering
danrod organization(s): OpenConcept Consulting Inc.
marvil07 organization(s): Isovera customer(s): Pegasystems
matt_paz
mattjones86
tmiguelv
finex volunteering
the_glitch
jungkunwar
phjou
kumkum29
jorgik organization(s): AnyforSoft, Drupal Ukraine Community
guicom volunteering
coaston
daveiano volunteering
farnoosh
liquidcms
socialnicheguru
rcodina
jeffschuler organization(s): Substrate Websoft customer(s): Cleveland Museum of Art
jmester13 volunteering
dqd volunteering organization(s): MAROQQO studios
jlbrewster47
prashant.c volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
abh.ai volunteering organization(s): QBurst
nick hope
jayelless
Git commit message
Commit types
  • 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

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.