Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
tobby organization(s): Phase2 customer(s): Phase2
pryrios
perignon
berdir organization(s): MD Systems GmbH
andreperazzi
pianomansam
mike82
mpastas organization(s): Globant
pierrelbz organization(s): Actency
mglaman organization(s): Bluehorn Digital
ugolek
vladbo organization(s): EPAM
grimreaper volunteering organization(s): Smile
darvanen
kevineinarsson volunteering
s_leu organization(s): Tag1 Consulting, Inc.
kksandr
hmdnawaz volunteering
slasher13 volunteering organization(s): Wolters Kluwer
shiv_sharma organization(s): Melity
devkinetic
o'briat volunteering organization(s): Capgemini
dave reid volunteering organization(s): Lullabot
dave.weiner volunteering
b n pandey organization(s): TO THE NEW
fraserthompson
nickdickinsonwilde volunteering
steinmb organization(s): University Of Bergen
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.