Skip to content
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

feature/rename-workflows-to-have-manual #29

Merged
merged 1 commit into from
Apr 24, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Get next update and verify dates
name: Manual Get next update and verify dates

on:
workflow_dispatch:
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/run-qa-test-manual.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: Run QA Test
name: Manual Run QA Test

on:
workflow_dispatch:
Expand Down
2 changes: 1 addition & 1 deletion docs/get_next_uv_dates.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
## GitHub Actions (for collaborators+ only)

1. Visit https://github.com/SIGLA-GU/siglatools/actions.
2. From the list of workflows, select `Get next update and verify dates`.
2. From the list of workflows, select `Manual Get next update and verify dates`.
3. Click on the `Run workflow` dropdown button.
4. Enter a start date and an end date. Make sure they are in YYYY-MM-DD format and start date is less than or equal to end date.
5. Click on the green `Run workflow` button to run the workflow.
Expand Down
4 changes: 2 additions & 2 deletions docs/run_qa_test.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
## GitHub Actions (for collaborators+ only)

1. Visit https://github.com/SIGLA-GU/siglatools/actions.
2. From the list of workflows, select `Run QA Test`.
2. From the list of workflows, select `Manual Run QA Test`.
3. Click on the `Run workflow` dropdown button.
4. Enter a list of `spreadsheetId`s, delimited by `,`. For example `spreadsheetId-1,spreadsheetId-2,spreadsheetId-3`.
5. Enter a database environment, `staging` or `production`. Choose `staging` if you want to compare the spreadsheet(s) in step 4 with the `staging` database. Choose `production` if you want to compare the spreadsheet(s) in step 4 with the `production` database.
Expand All @@ -26,7 +26,7 @@
8. On the workflow details page, once the run is finished click on the `qa-test-artifact` to download a zip file.

## QA Test Artifact Zip File
The zip file contains any mismatches between the data in the GoogleSheet and the data in the database. One file for each institution, if there are mismatches between the institution in the GoogleSheet and the institution in the database. The files are organized by the spreadsheet they belong to. There is an additional file `extra-institutions.csv`, which contains institutions in the database, but for some reason, doesn't have a counterpart institution in the GoogleSheet. If there are no files in zip file, then the QA script found no mismatches for the given spreadsheets.
The zip file contains any mismatches between the data in the GoogleSheet and the data in the database. One file for each institution, if there are mismatches between the institution in the GoogleSheet and the institution in the database. The files are organized by the spreadsheet they belong to. There is an additional file `extra-institutions.csv`, which contains institutions in the database, but for some reason, doesn't have a counterpart institution in the GoogleSheet. If there are no files in the zip file, then the QA script found no mismatches for the given spreadsheets.


## Spreadsheet Ids Format
Expand Down