Contribution records
Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): The Linux Foundation
ricardoamaro ricardoamaro volunteering organization(s): Acquia
antojose antojose volunteering
opdavies opdavies volunteering
jjchinquist jjchinquist organization(s): drunomics, Drupal Austria
bibliophileaxe bibliophileaxe organization(s): Discovery Garden
hansa11 hansa11 organization(s): Ramsalt Lab
jennydumitrescu jennydumitrescu volunteering
jovan1348 jovan1348 organization(s): acolono GmbH
nico_kuoni nico_kuoni
alexj12 Alexj12 organization(s): Zoocha
antonellasevero antonellasevero
mohit_aghera mohit_aghera organization(s): PreviousNext
sinduri sindurig organization(s): drunomics
vulcanr vulcanr volunteering organization(s): Annertech
bletch bletch
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
zoocha will ZoochaWill organization(s): Zoocha
issa.haddadin issahh volunteering organization(s): Nestlé
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.