-
-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Top Location is misleading #2
Labels
F-planned
New feature or request
Comments
amaury1093
pushed a commit
that referenced
this issue
Jun 30, 2019
amaury1093
added a commit
that referenced
this issue
Oct 15, 2019
* add GitHub actions (#283) Current steps: 1. Checkout 2. yarn install and lint 3. yarn test * Sathia27 GitHub actions (#2) * #283 Add github actions * fix(#283): remove unused lines in github actions * fix(#283): remove yarn install * fix(#283): add checkout actions * fix(#283): add CI on PR * fix(#283): test and setup as multiple job, remove travis * feat(#283): add github action badge, fix multi job * fix(#283): fix yaml syntax * fix(#283): fix yaml parsing issue - workflow * fix(#283): fix steps github actions * test(#283): test multi jobs * test(#283): test multiple jobs * test(#283): test multi job in actions * test(#283): test multi jobs with steps * test(test multi jobs): * test(#283): add multi jobs steps * test(#283): run multi jobs * test(#283): add multi job action * test(#283): multi jobs action * test(#283): add runs-on in all jobs * test(#283): add test job * test(#283): refactored jobs in github actions * fix(#283): fix multi job issue - github actions * test(#283): fix multi job build * test(#283): fix indentation * feat(#238): fix multi job failure * test(#283): add synchronous job * test(#283): fix yarn test * test(#238): moving from yaml to workflow * ci(#283): fix multi job failures * test(#283): run multi jobs * ci(#283): run yarn test without install * ci(#283): run yarn test in separate job * Update .github/workflows/main.yml Co-Authored-By: Amaury Martiny <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One user reported that the location was wrong, because he was in Detroit and the location was showing Windsor (next to Detroit).
I explained to him that it's probably because the closest air monitoring system was in Windsor.
Might need to think how to make this distinction clearer.
Also see:
The text was updated successfully, but these errors were encountered: