Contribution records
Contributors

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

Give credit to everyone
somebodysysop somebodysysop
shelane shelane
jrglasgow jrglasgow
le72 le72
andras_szilagyi Andras_Szilagyi customer(s): European Commission and European Union Institutions, Agencies and Bodies
kingdutch Kingdutch organization(s): Open Social
ben_drupal ben_drupal
pcate PCate
dabbor dabbor organization(s): Salsa Digital
mmenavas mmenavas volunteering
brt brt
caesius caesius organization(s): Forum One
bbombachini bbombachini organization(s): Northern Commerce
naveenvalecha naveenvalecha organization(s): Morpht customer(s): Morpht
abhisekmazumdar abhisekmazumdar organization(s): Morpht customer(s): Morpht
dylan donkersgoed DylanDonkersgoed organization(s): Northern Commerce
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.