Issue
Contribution records
Contributors

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

Give credit to everyone
yahyaalhamad organization(s): Sprintive
johnpitcairn
trevorbradley
berdir organization(s): MD Systems GmbH
matthieuscarset volunteering
keopx organization(s): Front ID, Isarea
bramdriesen volunteering organization(s): Capgemini
rbrownell organization(s): Aptitude Digital
vladanr
miro_dietiker organization(s): MD Systems GmbH
nterbogt volunteering organization(s): Flight Centre Travel Group
mistrae
ivrh organization(s): Salsa Digital, TrueCMS Pty. Ltd.
sershevchyk volunteering organization(s): Drupal Ukraine Community
Prez13
donaldinou
tom m fallon
Michael Maaß
ben.kyriakou volunteering organization(s): Cogapp
m.abdulqader organization(s): Sprintive
hanmant.sapkal
stefan.korn organization(s): Stefan Korn - Webentwicklung
e-l-s-e
kobe.vervoort
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.