-
Notifications
You must be signed in to change notification settings - Fork 20
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
Use nextstrain/ingest #412
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 tasks
victorlin
force-pushed
the
victorlin/centralized-ingest-git-subrepo
branch
2 times, most recently
from
August 11, 2023 13:08
3cffe01
to
aafc680
Compare
subrepo: subdir: "vendored" merged: "1eb8b30" upstream: origin: "https://github.com/nextstrain/ingest" branch: "main" commit: "1eb8b30" git-subrepo: version: "0.4.6" origin: "https://github.com/ingydotnet/git-subrepo" commit: "110b9eb"
The previous commit was created by the following command: git subrepo clone https://github.com/nextstrain/ingest vendored Add a section in the README on how to use this directory in the future.
Remove the copies in this repo and update references.
Both the centralized `trigger` and `trigger-on-new-data` take an owner/repo pair as the first argument.
Remove the copies in this repo and update references. Add new positional arguments required by the centralized scripts.
victorlin
force-pushed
the
victorlin/centralized-ingest-git-subrepo
branch
from
August 15, 2023 18:49
aafc680
to
6ce947e
Compare
joverlee521
approved these changes
Aug 24, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of proposed changes
Begin usage of centralized ingest scripts and add details on how to pull new updates from the central repo.
Related issue(s)
Testing
Checks pass (Update-image failure is unrelated and can be ignored. It was triggered by a non-functional change in update-image.yml).
Run GenBank fetch and ingest on PR branch, verify successful run.
Evidence
I checked for the presence of
✅ This pipeline has successfully finished 🎉
in the AWS Batch logs.I also spot checked some lines in the generated metadata file:
Run GISAID fetch and ingest on PR branch, verify successful run.
Evidence
Since I already checked an output file in the GenBank run, here I just checked for the presence of
✅ This pipeline has successfully finished 🎉
in the AWS Batch logs.Post-merge: Slack notifications still work as intended.