Issue
Contribution records
Contributors

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

Give credit to everyone
chi
pifagor organization(s): GOLEMS GABB customer(s): GOLEMS GABB
alexpott organization(s): Acro Commerce
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
yobottehg
ndobromirov organization(s): JAKALA (formerly FFW)
kala4ek volunteering organization(s): DrupalJedi
fabianx volunteering
elaman volunteering customer(s): imash
franz
sanjayk volunteering organization(s): Material customer(s): Drupal India Association
berdir organization(s): MD Systems GmbH
neclimdul organization(s): APQC
joachim volunteering organization(s): Factorial.io
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
andypost volunteering organization(s): Skilld
smustgrave organization(s): Mobomo
vakulrai volunteering organization(s): QED42 customer(s): QED42
mxr576 volunteering organization(s): Pronovix
anybody volunteering organization(s): DROWL.de
ankitv18 volunteering organization(s): Acquia
grasmash
wim leers volunteering organization(s): Acquia
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
joshua.boltz
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.