Issue
Contribution records
Contributors

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

Give credit to everyone
gmercer
olli
andypost volunteering organization(s): Skilld
marabak organization(s): Lumini
cferthorney
stella organization(s): Annertech
droplet
michielnugter volunteering organization(s): Synetic
slasher13 volunteering organization(s): Wolters Kluwer
lendude organization(s): ezCompany, Noctilaris
ericmulder1980 volunteering
sanduhrs organization(s): erdfisch
nod_ volunteering organization(s): OVHcloud
anavarre organization(s): Acquia
webchick organization(s): Acquia
dww volunteering
alexpott organization(s): Thunder
gaydamaka volunteering organization(s): JAKALA (formerly FFW)
timmillwood organization(s): Pfizer, Inc.
lauriii organization(s): Acquia
tim.plunkett
twod
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.