Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
capysara organization(s): Bounteous
johnwebdev
finex volunteering
phjou
alexmoreno
shubhangi1995
bradallenfisher
sadman
doostinharrell organization(s): Avid New Media
mr_scumbag organization(s): Code Journeymen
smustgrave organization(s): Mobomo
pierregermain
nsciacca
goz organization(s): Iosan
ranjith_kumar_k_u organization(s): Zyxware Technologies
mohanrajthangarasu organization(s): Opendrops
dalemoore
seanb organization(s): iO
chrisscrumping
delacosta456
atowl
frondeau
fabrondeau
robbdavis
mark.labrecque organization(s): Affinity Bridge
tim.plunkett organization(s): Acquia
hawkeye.twolf organization(s): Lullabot
geek-merlin organization(s): Geeks4Change, MachbarMacher
aaron.ferris
Alana Corrêa
flyke
dragos-dumi
drdam
apotek
vasike organization(s): DEHN digital solutions GmbH
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.