├── .github
├── FUNDING.yml
├── ISSUE_TEMPLATE
│ ├── bug_report.md
│ ├── feature_request.md
│ └── improve_existing_docs.md
├── labels.json
└── pull_request_template.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── INSTRUCTIONS.md
├── LICENSE
├── README.md
├── icon.png
├── index.html
├── index.php
├── script.js
├── style.css
├── style.css.map
├── style1.css
└── vaccine1.jpg
/.github/FUNDING.yml:
--------------------------------------------------------------------------------
1 |
2 | # These are supported funding model platforms
3 |
4 | github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
5 | patreon: # Replace with a single Patreon username
6 | open_collective: # Replace with a single Open Collective username
7 | ko_fi: # Replace with a single Ko-fi username
8 | tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
9 | community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
10 | liberapay: # Replace with a single Liberapay username
11 | issuehunt: # Replace with a single IssueHunt username
12 | otechie: # Replace with a single Otechie username
13 | custom: ["https://paypal.me/ashish2030",
14 | "https://www.buymeacoffee.com/ashish2030"]
15 | # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
16 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ### **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | ### **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | ### **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | ### Which Program are you part of?
24 |
28 | - [ ] DCP21
29 | - [ ] Any other
30 |
31 | ### **Screenshots**
32 | If applicable, add screenshots to help explain your problem.
33 |
34 | ### **Additional context**
35 | Add any other context about the problem here.
36 | ****
37 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | ### Is your feature request related to a problem? Please describe.
11 | A clear and concise description of what the problem is.
12 |
13 | ### Describe the solution you'd like
14 | A clear and concise description of what you want to happen.
15 |
16 | ### Describe alternatives you've considered
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | ### Describe how this feature will be useful to our readers.
20 | A clear and concise description of how this feature will be useful for our other readers.
21 |
22 | ### Which Program are you part of?
23 |
27 | - [ ] DCP21
28 | - [ ] Any other
29 |
30 | ### Additional context
31 | Add any other context or screenshots about the feature request here.
32 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/improve_existing_docs.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Documentation Change
3 | about: Help us in improve Documentation
4 | title: ''
5 | labels: 'Documentation'
6 | assignees: ''
7 |
8 | ---
9 |
10 |
11 | ### What part(s) of the documentation would you like to see updated?
12 |
13 |
14 |
15 | ### Which Program are you part of?
16 |
20 | - [ ] DCP21
21 | - [ ] Any other
22 |
23 | ### Additional information
24 |
25 |
26 |
--------------------------------------------------------------------------------
/.github/labels.json:
--------------------------------------------------------------------------------
1 | [
2 | {
3 | "name": "good first issue",
4 | "description": "This issue is good for first timers",
5 | "color": "a9e3ff"
6 | },
7 | {
8 | "name": "🆘 help wanted",
9 | "description": "This issue needs help ! Please help if possible !",
10 | "color": "ff00ff"
11 | },
12 | {
13 | "name": "🟧 Level3 ",
14 | "description": "This issue will be considered as level 3 issue for DCP21.Points will be 40.",
15 | "color": "ff9f1c"
16 | },
17 | {
18 | "name": "🟨 Level2 ",
19 | "description": "This issue will be considered as level 2 issue for DCP21.Points will be 20",
20 | "color": "ffcc00"
21 | },
22 | {
23 | "name": "🟩 Level1 ",
24 | "description": "This issue will be considered as level 1 issue for DCP21.Points will be 10",
25 | "color": "cfda2c"
26 | },
27 | {
28 | "name": "🟪 Level0 ",
29 | "description": "This issue will be considered as level 0 issue for DCP21.Points will be 5",
30 | "color": "aa00de"
31 | },
32 | {
33 | "name": " DCP21 ",
34 | "description": "This issue will be considered for DCP 21",
35 | "color": "d93f0b"
36 | },
37 | {
38 | "name": " 🤩 Up for Grab ",
39 | "description": "This issue is not yet assigned to anyone ! Grab It !",
40 | "color": "bf00ff"
41 | }
42 | ]
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | ## Related Issue
2 |
3 | - Info about the related issue
4 |
5 | Closes: #[issue number that will be closed through this PR]
6 |
7 | ### Describe the changes you've made
8 |
9 | Give a clear description what modifications you have made
10 |
11 | ## Type of change
12 |
13 | What sort of change have you made:
14 |
18 | - [ ] Bug fix (non-breaking change which fixes an issue)
19 | - [ ] New feature (non-breaking change which adds functionality)
20 | - [ ] Code style update (formatting, local variables)
21 | - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
22 | - [ ] This change requires a documentation update
23 |
24 | ## Mention any unusual behaviour of your code (Write NA if not)
25 | Any unusual behaviour of your code
26 |
27 | ## Checklist:
28 |
32 | - [ ] My code follows the guidelines of this project.
33 | - [ ] I have performed a self-review of my own code.
34 | - [ ] I have commented my code, particularly wherever it was hard to understand.
35 | - [ ] My changes generate no new warnings.
36 | - [ ] Any dependent changes have been merged and published in downstream modules.
37 |
38 |
39 | ### Which Program are you part of?
40 |
44 | - [ ] DCP21
45 | - [ ] Any other
46 |
47 | ## Additional Info (optional)
48 | Any additional information you want to give
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 |
2 | Code of Conduct
3 |
4 |
5 | ### Our Pledge
6 |
7 | We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
8 |
9 | We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
10 |
11 | ### Our Standards
12 |
13 | Examples of behavior that contributes to a positive environment for our community include:
14 |
15 | Demonstrating empathy and kindness toward other people
16 | Being respectful of differing opinions, viewpoints, and experiences
17 | Giving and gracefully accepting constructive feedback
18 | Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
19 | Focusing on what is best not just for us as individuals, but for the overall community
20 | Examples of unacceptable behavior include:
21 |
22 | The use of sexualized language or imagery, and sexual attention or advances of any kind
23 | Trolling, insulting or derogatory comments, and personal or political attacks
24 | Public or private harassment
25 | Publishing others’ private information, such as a physical or email address, without their explicit permission
26 | Other conduct which could reasonably be considered inappropriate in a professional setting
27 |
28 | ### Enforcement Responsibilities
29 |
30 | Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
31 |
32 | Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
33 |
34 | ### Scope
35 |
36 | This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
37 |
38 | ### Enforcement
39 |
40 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.
41 |
42 | All community leaders are obligated to respect the privacy and security of the reporter of any incident.
43 |
44 | ### Enforcement Guidelines
45 |
46 | Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
47 |
48 | #### 1. Correction
49 |
50 | Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
51 |
52 | Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
53 |
54 | #### 2. Warning
55 |
56 | Community Impact: A violation through a single incident or series of actions.
57 |
58 | Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
59 |
60 | #### 3. Temporary Ban
61 | Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
62 |
63 | Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
64 |
65 | #### 4. Permanent Ban
66 | Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
67 |
68 | Consequence: A permanent ban from any sort of public interaction within the community.
69 |
70 | ### Attribution
71 |
72 | This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][version].
73 |
74 | Community Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/inclusion).
75 |
76 | [homepage]: http://contributor-covenant.org
77 | [version]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 |
2 | Contribution Guidlines
3 |
4 |
5 | We want contributing to iRead Blog Project to be fun, enjoyable, and educational for anyone and everyone. All contributions are welcome, including issues, new docs as well as updates, and more.
6 |
7 | Please note we have a [code of conduct](https://github.com/ashutoshkrris/iRead/blob/master/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
8 |
9 | Before you begin:
10 | - Check out the [existing issues](https://github.com/ashutoshkris/iRead/issues).
11 |
12 | ## Don't see your issue? Open one
13 |
14 | If you spot something new, open an issue using a [template](https://github.com/ashutoshkris/iRead/issues/new/choose). We'll use the issue to have a conversation about the problem you want to fix.
15 |
16 | ## How to Open a Pull Request
17 |
18 | A big part of contributing to open source is submitting changes to a project: improvements to source code or tests, updates to docs content, even typos or broken links. This doc will cover what you need to know to **open a pull request**.
19 |
20 | In case you aren’t familiar, here’s how the folks at GitHub [define a pull request](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/about-pull-requests):
21 |
22 | > *Pull requests let you tell others about changes you've pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.*
23 |
24 | iRead Blog Project uses the PR process to review and test changes before they’re added to Project's GitHub repository. Anyone can open a pull request. The same process is used for all contributors, whether this is your first open source contribution or you’re a core member of the iRead Blog Project Team.
25 |
26 | When someone wants to contribute to any repo, they open a request to pull their code into the repo.
27 |
28 | ### Opening PRs in iRead Blog Project
29 |
30 | For any kind of change to files in our repo, you can follow the below steps. Be sure to check out additional tips for contributing to various parts of the repo later in this doc, such as docs changes, starters, or code improvements and tests.
31 |
32 | * [Fork and clone the repo](#fork-clone-and-branch-the-repository).
33 | * Run `pub get` to pull in all the dependencies.
34 | * Make your changes to the project.
35 | * [Create a branch in Git](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) to isolate your changes:
36 | ```
37 | git checkout -b
38 | ```
39 | * Once you have changes in Git you want to push, add them and create a commit.
40 | * Using a dot character . will add all untracked files in the current directory and subdirectories.
41 | ```
42 | git add .
43 | ```
44 | * Add any specific file using the command :
45 | ```
46 | git add
47 | ```
48 | * Commit your changes using the command :
49 | ```
50 | git commit -m "your message here"
51 | ```
52 | * Push your changes to your fork, assuming it is set up as origin:
53 | ```
54 | git push origin head
55 | ```
56 |
57 | ### Update your fork with the latest original repo changes
58 |
59 | Our repo is very active, so it’s likely you’ll need to update your fork with the latest changes to be able to merge in your code. This requires adding original repo as an upstream remote:
60 |
61 | * Set our repo URL as a remote source. The name of the remote is arbitrary; this example uses upstream.
62 | ```
63 | git remote add upstream
64 | ```
65 | * Fetch the latest changes from our repo:
66 | ```
67 | git fetch upstream master
68 | ```
69 | * In the branch you want to update, merge any changes from our repo into your fork:
70 | ```
71 | git merge upstream/master
72 | ```
73 | * Once your branch is in good working order, push the changes to your fork:
74 | ```
75 | git push origin head
76 | ```
77 |
78 | ## Fork, clone, and branch the repository
79 |
80 | * Fork the official [iRead Blog Project](https://github.com/ashutoshkrris/iRead) repository.
81 | * Clone the fork:
82 | ```
83 | git clone https://github.com/ashutoshkrris/iRead.git
84 | ```
85 | * Set up repo and install dependencies.
86 | * Create your branch : `git checkout -b `
87 |
88 |
89 |
--------------------------------------------------------------------------------
/INSTRUCTIONS.md:
--------------------------------------------------------------------------------
1 | #### GIT AND GITHUB
2 | ***
3 | Before continuing we want to clarify the difference between Git and Github. Git is a version control system(VCS) which is a tool to manage the history of our Source Code. GitHub is a hosting service for Git projects.
4 |
5 | We assume you have created an account on Github and installed Git on your System.
6 |
7 | Now tell Git your name and E-mail (used on Github) address.
8 |
9 | ``` $ git config --global user.name "YOUR NAME" ```
10 | ```$ git config --global user.email "YOUR EMAIL ADDRESS"```
11 | This is an important step to mark your commits to your name and email.
12 |
13 | ### FORK A PROJECT -
14 | ***
15 | You can use github explore - https://github.com/explore to find a project that interests you and match your skills. Once you find your cool project to workon, you can make a copy of project to your account. This process is called forking a project to your Github account. On Upper right side of project page on Github, you can see -
16 |
17 |
18 |
19 | Click on fork to create a copy of project to your account. This creates a separate copy for you to workon.
20 |
21 | ### FINDING A FEATURE OR BUG TO WORKON -
22 | ***
23 | Open Source projects always have something to workon and improves with each new release. You can see the issues section to find something you can solve or report a bug. The project managers always welcome new contributors and can guide you to solve the problem. You can find issues in the right section of project page.
24 |
25 |
26 |
27 | ### CLONE THE FORKED PROJECT -
28 | ***
29 | You have forked the project you want to contribute to your github account. To get this project on your development machine we use clone command of git.
30 |
31 | ```$ git clone https://github.com//.git```
32 | Now you have the project on your local machine.
33 |
34 | ### ADD A REMOTE (UPSTREAM) TO ORIGINAL PROJECT REPOSITORY
35 | ***
36 | Remote means the remote location of project on Github. By cloning, we have a remote called origin which points to your forked repository. Now we will add a remote to the original repository from where we had forked.
37 |
38 | ```$ cd ```
39 | ```$ git remote add upstream https://github.com//.git```
40 | You will see the benefits of adding remote later.
41 |
42 | ### SYNCHRONIZING YOUR FORK -
43 | ***
44 | Open Source projects have a number of contributors who can push code anytime. So it is necessary to make your forked copy equal with the original repository. The remote added above called Upstream helps in this.
45 |
46 | ```$ git checkout master```
47 | ```$ git fetch upstream```
48 | ```$ git merge upstream/master```
49 | ```$ git push origin master```
50 | The last command pushes the latest code to your forked repository on Github. The origin is the remote pointing to your forked repository on github.
51 |
52 | ### CREATE A NEW BRANCH FOR A FEATURE OR BUGFIX -
53 | ***
54 | Normally, all repositories have a master branch which is considered to remain stable and all new features should be made in a separate branch and after completion merged into master branch. So we should create a new branch for our feature or bugfix and start working on the issue.
55 |
56 | ```$ git checkout -b ```
57 | This will create a new branch out of master branch. Now start working on the problem and commit your changes.
58 |
59 | ```$ git add --all```
60 | ```$ git commit -m ""```
61 | The first command adds all the files or you can add specific files by removing -a and adding the file names. The second command gives a message to your changes so you can know in future what changes this commit makes. If you are solving an issue on original repository, you should add the issue number like #35 to your commit message. This will show the reference to commits in the issue.
62 |
63 | ### REBASE YOUR FEATURE BRANCH WITH UPSTREAM-
64 | ***
65 | It can happen that your feature takes time to complete and other contributors are constantly pushing code. After completing the feature your feature branch should be rebase on latest changes to upstream master branch.
66 |
67 | ```$ git checkout ```
68 | ```$ git pull --rebase upstream master```
69 | Now you get the latest commits from other contributors and check that your commits are compatible with the new commits. If there are any conflicts solve them.
70 |
71 | ### SQUASHING YOUR COMMITS-
72 | ***
73 | You have completed the feature, but you have made a number of commits which make less sense. You should squash your commits to make good commits.
74 |
75 | ```$ git rebase -i HEAD~5```
76 | This will open an editor which will allow you to squash the commits.
77 |
78 | ### PUSH CODE AND CREATE A PULL REQUEST -
79 | ***
80 | Till this point you have a new branch with the feature or bugfix you want in the project you had forked. Now push your new branch to your remote fork on github.
81 |
82 | ```$ git push origin ```
83 | Now you are ready to help the project by opening a pull request means you now tell the project managers to add the feature or bugfix to original repository. You can open a pull request by clicking on green icon -
84 |
85 |
86 |
87 | Remember your upstream base branch should be master and source should be your feature branch. Click on create pull request and add a name to your pull request. You can also describe your feature.
88 |
89 | Awesome! You have made your first contribution. If you have any doubts please let me know in the comments.
90 |
91 | #### BE OPEN!
92 |
93 | There are templates created by us to ease some of your work and for a structured documentation
94 |
95 | #### Issue Templates - [Click Here](https://github.com/ashutoshkrris/iRead/issues/new/choose)
96 |
97 |
98 | ### Pull Request Templates-[Click Here](.github/pull_request_template.md)
99 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2021 Ashish Kumar
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
59 |
60 |
61 |
62 | ## Contributing
63 |
64 | ### Setting-up the project
65 |
66 | * Fork the Repository
67 | * Clone the repository to your local machine
68 |
69 | `$ git clone https://github.com//Vaccine-near-me-Using-Cowin-Government-API`
70 | * Change directory to 'Vaccine-near-me-Using-Cowin-Government-API'
71 |
72 | `$ cd Vaccine-near-me-Using-Cowin-Government-API`
73 | * Add a reference to the original repository
74 |
75 | `$ git remote add upstream https://github.com/ashish2030/Vaccine-near-me-Using-Cowin-Government-API.git`
76 |
77 |
78 | #### 💡️ **Pro Tip:**
79 | * Always keep your master branch in sync with the main repository (by running `$ git pull upstream master` on your local master branch).
80 | * Always create a new branch before making any changes (`$ git checkout -b `), never ever make any changes directly on the master branch.
81 |
82 |
83 |
84 |
85 | ## 💥 How to Contribute ?
86 | - If you wish to contribute kindly check the [CONTRIBUTING.md](https://github.com/ashish2030/Vaccine-near-me-Using-Cowin-Government-API/blob/master/CONTRIBUTING.md)🤝
87 | - If you are completely new to Open Source, read the [Instructions](https://github.com/ashish2030/Vaccine-near-me-Using-Cowin-Government-API/blob/master/INSTRUCTIONS.md).
88 | - Please follow the [CODE OF CONDUCT](https://github.com/ashish2030/Vaccine-near-me-Using-Cowin-Government-API/blob/master/CODE_Of_CONDUCT.md)
89 |
90 | ## 💥 Project Maintainers👨🏫:
91 |
92 | | |
93 | | :------------------------------------------------------------------------------------------: | :------------------------------------------------------------------------------------------:
94 | | [Project Admin](https://github.com/Ashish2030)\* | [Mentor](https://github.com/MukulKolpe)\* |
95 |
96 |
97 | ## ✨ Contributors
98 | ### Thanks go to these Wonderful People 👨🏻💻
99 |
100 |
101 |
102 |
103 | 🚀 Contributions of any kind are welcome!
104 |
105 |
106 |
107 |
108 |
109 | ## 💥 Open Source Programs we have been a part of:
110 |