Issue
Contribution records
Contributors

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

Give credit to everyone
vladimiraus organization(s): Tomato Elephant Studio
andypost volunteering organization(s): Skilld
abhinesh volunteering
m4olivei organization(s): Lullabot customer(s): IBM
murilohp organization(s): CI&T
muskan_mahajan organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
joachim organization(s): Factorial.io
abhinavk organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
pfrenssen organization(s): Liip
smulvih2 organization(s): Cinder Systems Corp., OpenPlus
joshf organization(s): CivicActions customer(s): National Science Foundation
aurelianzaha organization(s): jobiqo - job board technology
larowlan organization(s): PreviousNext
rajab natshah organization(s): Vardot customer(s): Vardot
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.