Contribution records
Contributors

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

Give credit to everyone
amateescu amateescu organization(s): Pfizer, Inc.
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
berdir berdir organization(s): MD Systems GmbH
phenaproxima phenaproxima organization(s): Acquia
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
slashrsm slashrsm organization(s): MD Systems GmbH
mpdonadio matthew.donadio organization(s): DiD Agency
jofitz jofitz organization(s): ComputerMinds
andypost andypost volunteering organization(s): Skilld
voleger voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
larowlan larowlan organization(s): PreviousNext
mikelutz mdlutz volunteering organization(s): ICON Interactive
johnwebdev johnwebdev
chr.fritsch chr.fritsch organization(s): Thunder
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.