Contribution records
Contributors

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

Give credit to everyone
mikeryan mikeryan organization(s): Acquia
mitrpaka mitrpaka volunteering
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
jofitz jofitz organization(s): ComputerMinds
NiklasBr NiklasBr
quietone quietone volunteering
wturrell wturrell
summit summit
steinmb steinmb volunteering
shaktik shaktik volunteering organization(s): Material customer(s): Drupal India Association
sseto Sseto
azussman azussman
mikelutz mdlutz volunteering organization(s): Four Kitchens
catch catch organization(s): Third and Grove
kapilv kapilkumar0324 volunteering organization(s): Innoraft customer(s): Drupal Care
benjifisher benjifisher organization(s): FRUITION
anushrikumari anushri19 organization(s): OpenSense Labs
cosolom cosolom
sokru kallevu volunteering
clemens.tolboom clemenstolboom volunteering
savkaviktor16@gmail.com Saviktor organization(s): Skilld
wim leers wimleers organization(s): Acquia
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.