update master (#106)

* update development from master (#101)

* Update main.yml

* Update branch name

* Update SearchAttendee.vue

* Update Readme.md

* Update Readme.md

* creating staging mode for netlify

* Update Readme.md

* Update Readme.md

* fixed scanning and data processing (#105)

* renamed files and fixed first name not showing

* codacy readme + create clear store

* fix daily check in unaccessible

* fix camera

* create new utils

* checkin works completed

* complete registration

* fixed codacy

* fixed formatting

* readme codacy

---------

Co-authored-by: Mario Behling <mb@mariobehling.de>

Readme.md

@@ -7,17 +7,16 @@
 [![Twitter Follow](https://img.shields.io/twitter/follow/eventyay.svg?style=social&label=Follow&maxAge=2592000?style=flat-square)](https://twitter.com/eventyay)
 
 ## Communication
-
-Please join our [Mailing list](https://groups.google.com/forum/#!forum/open-event) or [chat channel](https://gitter.im/fossasia/open-event-frontend) to get in touch with the developers.
+Please join our [mailing list](https://groups.google.com/forum/#!forum/open-event) or [chat channel](https://gitter.im/fossasia/open-event-frontend) to get in touch with the developers.
 
 ## Installation
-
 Easily deployed on a variety of platforms. Detailed platform specific instructions have been provided below.
+
 ### Local
-Clone or Fork the codebase and following instructions [below](https://github.com/fossasia/open-event-checkin/tree/development/.github/workflows)
+Clone or Fork the codebase and following instructions [below](#running--development).
 
 ### Github Pages (using Github Actions)
-Refer to our [workflow](https://github.com/fossasia/open-event-checkin/tree/development/.github/workflows) for deployment
+Refer to the [workflow](https://github.com/fossasia/open-event-checkin/tree/development/.github/workflows) for deployment.
 
 ## Running / Development
 
@@ -69,13 +68,11 @@ npm build
 
 **Master branch**
 
-Deployed in a production environment at [https://checkin.eventyay.com](https://checkin-eventyay.com)
-It consumes the API exposed by master branch deployment of open event server, hosted at [https://api.eventyay.com](https://api.eventyay.com)
+Deployed in a production environment at [checkin.eventyay.com](https://checkin.eventyay.com) it consumes the API exposed by master branch deployment of open event server, hosted at [api.eventyay.com](https://api.eventyay.com).
 
 #### Development branch
 
-Only deployed locally with `npm run dev` or Netlify version when you make a pull request
-It consumes the API exposed by development branch of open event server, hosted at [https://test-api.eventyay.com](https://test-api.eventyay.com)
+Only deployed locally with `npm run dev` or Netlify when you make a pull request it consumes the API exposed by development branch of open event server, hosted at [test-api.eventyay.com](https://test-api.eventyay.com).
 
 ## Further Reading / Useful Links
 
@@ -98,9 +95,9 @@ It consumes the API exposed by development branch of open event server, hosted a
 
 ### Commits
 
-- Write clear meaningful git commit messages (Do read [https://chris.beams.io/posts/git-commit/](https://chris.beams.io/posts/git-commit/))
-- Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at [https://github.com/blog/1506-closing-issues-via-pull-requests](https://github.com/blog/1506-closing-issues-via-pull-requests) )
-- When you make very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at [https://davidwalsh.name/squash-commits-git](https://davidwalsh.name/squash-commits-git) )
+- Write clear meaningful git commit messages (Do read [chris.beams.io/posts/git-commit/](https://chris.beams.io/posts/git-commit/))
+- Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at [github.com/blog/1506-closing-issues-via-pull-requests](https://github.com/blog/1506-closing-issues-via-pull-requests) )
+- When you make very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at [davidwalsh.name/squash-commits-git](https://davidwalsh.name/squash-commits-git) )
 - When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
 
 ### Feature Requests and Bug Reports
@@ -116,4 +113,4 @@ When you file a feature request or when you are submitting a bug report to the [
 
 This project is currently licensed under the [Apache License version 2.0](LICENSE).
 
-To obtain the software under a different license, Please contact **[FOSSASIA](https://blog.fossasia.org/contact/)**.
+To obtain the software under a different license, Please contact [FOSSASIA](https://blog.fossasia.org/contact/).