Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
plach volunteering
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
criz organization(s): acolono GmbH
marcoscano volunteering organization(s): Lullabot customer(s): New Relic
sanket1007
charginghawk organization(s): Pegasystems
smustgrave organization(s): Mobomo
banoodle organization(s): Kanopi Studios
kosa ilma organization(s): Brainsum customer(s): The International Federation of Red Cross and Red Crescent Societies (IFRC), Tieto
ravi.shankar organization(s): OpenSense Labs
yovanny.gomez.oyola organization(s): Globant
mjpa organization(s): Zoocha
achap
rajiv.singh
uri_frazier
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.