Issue
Contribution records
Contributors

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

Give credit to everyone
ironkiat organization(s): Pixel Onion Pte Ltd
kostyashupenko organization(s): Skilld
chx
droplet
tstoeckler organization(s): erdfisch
alamowo
nesta_ organization(s): La Drupalera by Emergya
joelpittet volunteering
mukeshmukesh12 organization(s): gai Technologies Pvt Ltd
kiwimind organization(s): Investis Digital
starshaped volunteering
larowlan organization(s): PreviousNext
phenaproxima organization(s): Acquia
aaronchristian organization(s): Acro Commerce
yoroy organization(s): Roy Scholten
lauriii volunteering
shiva srikanth t volunteering organization(s): Melity
emma.maria organization(s): TES Global
star-szr volunteering
manjit.singh organization(s): Material
tim.clifford organization(s): Investis Digital
wim leers 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.