Issue
Contribution records
Contributors

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

Give credit to everyone
jeroent organization(s): iO
francewhoa organization(s): Ubertus
spartanic
Yete
krisrobinson
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
nerdstein volunteering organization(s): Hook 42
daggerhart volunteering organization(s): Hook 42
artematem organization(s): JAKALA (formerly FFW)
wturrell volunteering
baikho volunteering organization(s): Access (now GAIN)
andypost volunteering organization(s): Skilld
jcnventura organization(s): 1xINTERNET
orlando.thoeny organization(s): Namics
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
harshil.maradiya organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
moshe weitzman volunteering
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.