Issue
Contribution records
Contributors

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

Give credit to everyone
dasjo organization(s): Amazee Labs
joelpittet
jwilson3 organization(s): Bluespark
chi
hkirsman
autopoietic organization(s): Torchbox
natemow
hmartens
rominronin
ArchieV
rp7
gagarine volunteering
RAWDESK
artematem organization(s): JAKALA (formerly FFW)
imperator_99
yaronmiro volunteering
elaman volunteering customer(s): imash
prasannag volunteering customer(s): BORN Commerce
MoCart
maskedjellybean volunteering
hudri
shamsher_alam organization(s): Publicis Sapient
navid045
robert_t_taylor
wxman
khaled_webdev
jedihe organization(s): Council on Foreign Relations
markconroy organization(s): Annertech
jedgar1mx volunteering
sannminwin
gaspounet
alexborsody
star-szr volunteering
anonym-developer
Andre-B organization(s): Hubert Burda Media
manuel.adan organization(s): Arcovía Digital
lauris.kuznecovs@wunder.io
Denis Waßmann
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.