Issue
Contribution records
Contributors

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

Give credit to everyone
juampynr
mrharolda
luckydad
mogwaay
rudiedirkx
mvc organization(s): Evolving Web, The Linux Foundation
joachim
heykarthikwithu volunteering organization(s): Valuebound
malcomio organization(s): Capgemini
nagarseth volunteering
socialnicheguru
jyraya organization(s): European Commission and European Union Institutions, Agencies and Bodies
enriquelacoma
albapb
alex_optim organization(s): GOLEMS GABB customer(s): GOLEMS GABB
pifagor organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
jwilson3 organization(s): Bluespark
andralex organization(s): EPAM customer(s): EPAM
ulethjay
pendaco
mitchmac
vbard
sebastien m.
ion.macaria
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.