Issue
Contribution records
Contributors

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

Give credit to everyone
swentel organization(s): eps & kaas customer(s): Dropsolid
mishac
jibran organization(s): PreviousNext
upchuk volunteering
drcolossos organization(s): CYLEDGE
WidgetsBurritos organization(s): Rackspace
train organization(s): Keystone Click
adrianm6254
markdorison organization(s): Chromatic
anybody volunteering organization(s): DROWL.de
hugovk organization(s): Digia customer(s): Yle - Finnish Broadcasting Company
akshita
mturner20 volunteering organization(s): Northern Commerce
stevenx
zyla
shreya_r
shepparddigital
dylan donkersgoed
isa.bel
Gnanasampandan Velmurgan volunteering
rakesh.gectcr volunteering customer(s): Access (now GAIN)
davi.uezono organization(s): CI&T customer(s): Johnson & Johnson
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.