Issue
Contribution records
Contributors

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

Give credit to everyone
bladedu organization(s): SparkFabrik
dioni organization(s): Code Enigma
stefdewa organization(s): Calibrate
pub497 volunteering
andreasderijcke organization(s): Calibrate
juanjol volunteering organization(s): Metadrop
mullzk
jhuhta organization(s): Siili Solutions
catch organization(s): Third and Grove
dpacassi organization(s): Epsilon Labs customer(s): Unic
mschudders organization(s): Calibrate
flocondetoile organization(s): Flocon de toile
volkerk organization(s): Thunder
raffaelj
thomaswalther
andrerb organization(s): undpaul
bbu23 organization(s): Ninja Coders
sergeimalyshev volunteering
berdir organization(s): MD Systems GmbH
rolki volunteering organization(s): YMCA of the USA
bonrita organization(s): iO
mibstar
Git commit message
Commit types
  • 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

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.