Issue
Contribution records
Contributors

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

Give credit to everyone
eclipsegc
imalabya organization(s): Valuebound
dsnopek
fago organization(s): drunomics
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
lokapujya
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
jofitz organization(s): ComputerMinds
phenaproxima organization(s): Acquia
larowlan organization(s): PreviousNext
catch organization(s): Third and Grove
berdir organization(s): MD Systems GmbH
jonathan1055 volunteering
agentrickard organization(s): Palantir.net
cilefen volunteering
abramm organization(s): DevBranch customer(s): Creative Propulsion Labs
timodwhit
tim.plunkett organization(s): Acquia
samuel.mortenson organization(s): Acquia
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.