Contribution records
Contributors

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

Give credit to everyone
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
pvbergen pvbergen volunteering
the_g_bomb the_g_bomb organization(s): Zoocha
zaporylie zaporylie customer(s): Centarro
borisson_ borisson_ organization(s): Calibrate
dan2k3k4 dan2k3k4 organization(s): Amazee Labs
jpvos jpfox volunteering organization(s): React online customer(s): drupalnl
criz criz organization(s): acolono GmbH, Drupal Austria
catia_penas Catia_Penas volunteering organization(s): FreelyGive
dasjo dasjo volunteering organization(s): Liip
kristen pol kepol organization(s): Salsa Digital
allie micka vauxia organization(s): bluebird.io
gábor hojtsy goba organization(s): Acquia
imre gmelig meijling imre_gmelig_meijling volunteering organization(s): ronder
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.