Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
marcvangend volunteering organization(s): ronder
joycelam organization(s): ronder
sutharsan organization(s): ronder
BarisW organization(s): ronder
karlshea
casey volunteering organization(s): SWIS
quietone volunteering
alexpott volunteering
neclimdul
andypost volunteering organization(s): Skilld
effulgentsia organization(s): Acquia
catch organization(s): Third and Grove
borisson_ organization(s): Calibrate
idebr organization(s): iO
tyler36 organization(s): Inter Quest Co.,Ltd.
watergate organization(s): Sicse
mollux volunteering
giuseppe87
luismagr volunteering organization(s): Code Enigma
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
tisteegz
meeni_dhobale
gcb
philltran
joseph.olstad organization(s): Entreprise 7pro.ca Inc, Cinder Systems Corp.
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.