Download • Screenshots • Features • Building • Credits • Contributing • License
- Vaccine slot local notifications
- State and District selections
- Hide results having minimum age of 45
- Dark theme (if enabled on system)
To clone and run this app, you'll need Git and Node.js installed on your computer,
Starts the react-native bundler.
Builds and runs the app for Android.
Builds and runs the app for iOS.
Launches the test runner in the interactive watch mode.
This app uses the following amazing open source packages:
- Clone
- Create a
<type>-prefixed branch where<type>is a type from the below list - Make a pull request
We follow the conventional commit message spec. It's recommended that you read more about it below or on conventionalcommits.org.
Basically, the commit messages should be of the following form:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types include and are limited to:
| Type | Version Bump | Description and used for |
|---|---|---|
| feat | minor | New features |
| fix | patch | Fixing bugs |
| revert | patch | Reverting commits |
| perf | patch | Performance improvements |
| refactor | patch | Refactoring code without changing functionality |
| build | patch | Build-system changes (deps, webpack, etc.) |
| chore | patch | General chores like version bump, merges, etc |
| ci | patch | CI/CD related changes |
| docs | none | Documentation |
| test | none | Adding/improving tests |
| style | none | Code-style, formatting, white-space, etc |
- !: A commit that appends a
!after the type/scope, introduces a breaking API change. A BREAKING CHANGE can be part of commits of any type and introduces a major version bump. - A scope of
noreleasewith any commit message type will not bump a release version.
MIT
Neil Agarwal · GitHub @regalstreak · Twitter @regalstreak · LinkedIn @agarwal-neil