Contribution records
Contributors

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

Give credit to everyone
cweagans cweagans
msonnabaum msonnabaum
sun sun
catch catch organization(s): Third and Grove
Crell Crell organization(s): Upsun (formerly Platform.sh)
gdd heyrocker
pounard pounard
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
berdir berdir
dawehner dereine volunteering
jthorson jthorson
chx chx
jibran jibran volunteering
podarok podarok
damiankloip damiankloip
herom herom
webchick webchick
xjm xjm organization(s): Acquia
larowlan larowlan organization(s): PreviousNext
rcaracaus rcaracaus
klonos klonos
Mixologic Mixologic organization(s): Drupal Association
pwolanin pwolanin
yesct YesCT
cilefen cilefen
hussainweb hussainweb organization(s): Axelerant
neclimdul neclimdul organization(s): APQC
anavarre anavarre organization(s): Acquia
joelpittet joelpittet
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
david_garcia david_garcia_garcia
drupalshrek drupalshrek
damien tournoud damz
tim.plunkett tim.plunkett
claudiu.cristea claudiucristea
kim.pepper kimpepper
wim leers wimleers 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.