Contribution records
Contributors

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

Give credit to everyone
prudloff prudloff organization(s): Insite
eelkeblok eelkeblok organization(s): iO
nishavaghela NishaVaghela organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
sourabhjain sourabh_jain_419 organization(s): Valuebound customer(s): Valuebound
selwynpolit selwynpolit organization(s): Mighty Citizen
alphex alphex
energee energee volunteering organization(s): EPAM
bobooon robbiehobby
justcaldwell justcaldwell volunteering
dioni dioni organization(s): Code Enigma
shelane shelane
oakulm oakulm volunteering organization(s): Drontti Oy customer(s): Drontti Oy
gooddenis goodDenis volunteering
bob.hinrichs bob.hinrichs
gaëlg gaelg organization(s): Insite
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.