Issue
Contribution records
Contributors

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

Give credit to everyone
berdir organization(s): MD Systems GmbH
msankhala volunteering organization(s): Material
dagmar volunteering organization(s): Gizra
pavelculacov
keynone
surbz organization(s): Material
RAFA3L
alexpott organization(s): Acro Commerce, Thunder
scotwith1t organization(s): Mobomo customer(s): Vibrent Health
shaal volunteering organization(s): Palantir.net customer(s): Tableau
bnjmnm organization(s): Acquia
yahyaalhamad organization(s): Sprintive
anybody organization(s): DROWL.de
sic
johnwebdev
diego_mow volunteering organization(s): CI&T
mdupont organization(s): United Nations
tomsch
makeaweli
babis.p
steven buteneers organization(s): Synetic
dhirendra.mishra organization(s): Material, Valuebound customer(s): Valuebound
tim.plunkett organization(s): Acquia
thomas.frobieter organization(s): DROWL.de
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.