Contribution records
Contributors

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

Give credit to everyone
dixon_ dixon organization(s): Pfizer, Inc. customer(s): Pfizer, Inc.
fago fago organization(s): drunomics
Crell Crell organization(s): Upsun (formerly Platform.sh)
timmillwood timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
amateescu amateescu customer(s): Pfizer, Inc.
larowlan larowlan organization(s): PreviousNext
Bojhan bojhan volunteering
jibran jibran volunteering
catch catch organization(s): Third and Grove
agentrickard agentrickard organization(s): Palantir.net
webchick webchick organization(s): Acquia
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
berdir berdir organization(s): MD Systems GmbH
cosmicdreams cosmicdreams
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
xjm xjm organization(s): Acquia
swentel swentel
becw bec organization(s): Palantir.net
benjy benjy organization(s): PreviousNext
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
hass hass
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.