Contribution records
Contributors

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

Give credit to everyone
phenaproxima phenaproxima organization(s): Acquia
rainbowarray RainbowArray organization(s): Lullabot
fabianx Fabianx organization(s): Tag1 Consulting, Inc.
seanb seanB
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
berdir berdir organization(s): MD Systems GmbH
drugan drugan volunteering
andypost andypost volunteering organization(s): Skilld
xjm xjm organization(s): Acquia
vijaycs85 vijaycs85 volunteering
tanubansal tanubansal organization(s): Salsa Digital
longwave longwave organization(s): Full Fat Things
wim leers wimleers organization(s): Acquia
chr.fritsch chr.fritsch organization(s): Thunder
marcin maruszewski MarcinMaruszewski organization(s): RatioWeb
raman.b ramanbatra1709 organization(s): OpenSense Labs
avpaderno avpaderno volunteering
immaculatexavier immaculate.x volunteering organization(s): Material customer(s): Drupal India Association
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.