Contribution records
Draft
Contributors

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

Give credit to everyone
eelkeblok eelkeblok organization(s): iO, One Shoe
malcomio malcomio
chi Chi
dawehner dereine volunteering
jasonawant jwant organization(s): Current
wturrell wturrell volunteering
longwave longwave volunteering
geekygnr geekygnr organization(s): Lullabot
pameeela pameeela
alison alison volunteering
quietone quietone volunteering
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
benjifisher benjifisher organization(s): FRUITION
paulocs paulocs organization(s): CI&T
chetanbharambe chetan18 organization(s): QED42 customer(s): Drupal India Association
marcvangend marcvangend volunteering organization(s): ronder
danflanagan8 danflanagan8 organization(s): Horizontal
mlncn mlncn organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
smustgrave smustgrave organization(s): Mobomo
poker10 poker10 organization(s): ActivIT s.r.o.
star-szr star-szr volunteering organization(s): Northern Commerce
nick.ev nick.ev
samitk samit.310 organization(s): Material customer(s): Drupal India Association
liam morland lkmorlan organization(s): OpenPlus, Scouting Waterloo Region
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.