Contribution records
Contributors

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

Give credit to everyone
chrisfromredfin chrisfromredfin organization(s): Redfin Solutions, LLC
rkoller rkoller
jayhuskins jayhuskins organization(s): Redfin Solutions, LLC
tinto Tinto organization(s): The Savvy Few
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
philipnorton42 philipnorton42 volunteering organization(s): #! code (Hash Bang Code), Code Enigma
dydave DYdave organization(s): Code Enigma
lostcarpark lostcarpark volunteering
william.kan@oneyoungworld.com william_kan volunteering
greg.harvey greg.harvey organization(s): Code Enigma
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.