Issue
Contribution records
Contributors

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

Give credit to everyone
thaddeusmt
carlitus organization(s): Omitsis Consulting SL
stborchert organization(s): undpaul
volker23 volunteering
drs2034 volunteering
komlenic
attisan
geraldito
michaelvanh
summit
itaran
kwfinken organization(s): Michigan State University customer(s): Michigan State University
nicklasmf
gurjinder_pabla volunteering
petar_basic organization(s): drunomics
kid_baco
tepelena
inversed
plopesc organization(s): Cocomore AG customer(s): Nestlé
vacilando volunteering
mkindred
phjou
urvashi_vora organization(s): Valuebound customer(s): Valuebound
damienmckenna organization(s): Current
jcl324 volunteering organization(s): Clarity Innovations, Inc.
simohell organization(s): Druid
tim-diels organization(s): Calibrate
mark.gorman organization(s): Moore-Wilson
nicolas bouteille
vlad.dancer volunteering organization(s): Drupal Ukraine Community customer(s): Oomph, Inc., Xspace
dr. gubó organization(s): druplus
nick hope
albert volkman
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.