Issue
Contribution records
Contributors

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

Give credit to everyone
wendell
smustgrave organization(s): Mobomo
JJLems
darko_antunovic organization(s): Studio Present customer(s): Studio Present
klemendev volunteering organization(s): Pylo
taran2l organization(s): Lemberg Solutions
tyler36 organization(s): Inter Quest Co.,Ltd.
evilargest volunteering organization(s): Drupal Ukraine Community, Lemberg Solutions
cilefen
jhedstrom organization(s): Phase2
mlncn organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
mindaugasd volunteering
sirclickalot
sakiland volunteering
longwave organization(s): Full Fat Things
nod_ organization(s): Très Bien Tech customer(s): OPTASY, Palantir.net
malik.kotob organization(s): Pantheon
alina.basarabeanu
tim-diels organization(s): Calibrate
lukas.fischer organization(s): NETNODE AG
luke.leber
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.