Issue
Contribution records
Contributors

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

Give credit to everyone
nod_ volunteering
martin107 volunteering
mpdonadio organization(s): DiD Agency
droplet
dawehner
pfrenssen
alexpott volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
fafnirical
tizzo
effulgentsia organization(s): Acquia
mradcliffe organization(s): Kosada
20th
GrandmaGlassesRopeMan organization(s): Acquia
nedjo
David_Rothstein volunteering
webchick organization(s): Acquia
justafish volunteering
finne organization(s): Dx Experts
dmsmidt organization(s): Triquanta
michielnugter volunteering organization(s): Synetic
pingwin4eg volunteering
xjm organization(s): Acquia
borisson_ organization(s): Calibrate
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
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.