Contribution records
Contributors

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

Give credit to everyone
balazswmann balazswmann
boobaa boobaa organization(s): Pronovix
marcoscano marcoscano organization(s): Lullabot
phenaproxima phenaproxima organization(s): Acquia
pk188 pk188 organization(s): OpenSense Labs
dinesh18 Dinesh18 volunteering
seanb seanB
vijaycs85 vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
catch catch organization(s): Third and Grove
larowlan larowlan organization(s): PreviousNext
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
berdir berdir organization(s): MD Systems GmbH
xjm xjm organization(s): Acquia
nitebreed Nitebreed organization(s): Synetic
mycw1991 mycw1991
michael_wojcik michael_wojcik volunteering organization(s): Current
alexpott alexpott organization(s): Acro Commerce
effulgentsia effulgentsia organization(s): Acquia
wim leers wimleers volunteering organization(s): Acquia
chr.fritsch chr.fritsch organization(s): Thunder
govind.maloo govind.maloo organization(s): Salsa Digital
web-beest Web-Beest organization(s): Web-Beest customer(s): RIVM
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.