Contribution records
Contributors

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

Give credit to everyone
janes_p janes_p organization(s): SANTIS AG
cilefen cilefen organization(s): Institute for Advanced Study
jamesoakley JamesOakley volunteering
naheemsays nbz
BartNijs BartNijs
hermanP hermanP
spficklin spficklin
jshimota01 jshimota01
dimilias dimilias organization(s): Randstad Digital customer(s): European Commission and European Union Institutions, Agencies and Bodies
dkre dkre
geerlingguy geerlingguy organization(s): Midwestern Mac, LLC
ressa ressa organization(s): Ardea
podarok podarok organization(s): Drupal Ukraine Community, ITCare, Open Y customer(s): Drupal Ukraine Community, Open Y
djween djween
tr tr
longwave longwave organization(s): Full Fat Things
Mixologic Mixologic organization(s): Drupal Association
jpvivere jpvivere
joshua.boltz joshua.boltz organization(s): Current
freddy rodriguez Friedinand volunteering
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.