Issue
Contribution records
Contributors

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

Give credit to everyone
nod_
Crell
andypost volunteering organization(s): Skilld
yanniboi
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
damiankloip
dmouse
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
dixon_
jeqq organization(s): JAKALA (formerly FFW) customer(s): Pfizer, Inc.
ygerasimov
effulgentsia
dries
xjm organization(s): Acquia
pkosenko
keboca volunteering
constrict0r
AlxVallejo
catch organization(s): Third and Grove
jibran volunteering
slasher13 volunteering
sam152 volunteering organization(s): PreviousNext
cilefen volunteering
damien tournoud
wim leers organization(s): Acquia
kim.pepper
-enzo-
chr.fritsch
clemens.tolboom
decibel.places
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.