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

Check before creating by_assembly directories #459

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

tcezard
Copy link
Member

@tcezard tcezard commented Jul 17, 2024

Only create a symlink in the by assembly directory if the corresponding by_species directory exists

# Create a link from assembly folder to species_folder ex: by_assembly/GCA_000005005.5/zea_mays to by_species/zea_mays/GCA_000005005.5
create_symlink_to_species_folder_from_assembly_folder(current_release_assembly_info, release_properties,
public_release_assembly_folder)
if current_release_assembly_info["num_rs_to_release"] > 0:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Debatable whether this is even a good idea, but elsewhere we check both num_rs_to_release and should_be_released... should we do the same here to be consistent?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you're right that this is inconsistent with what is done elsewhere.
The reason I've only used the num_rs_to_release is because originally the should_be_released flag really meant that the release pipeline should be run not that the data should be copied and in previous version of the release automation should_be_released=false and num_rs_to_release>0 was used to denote release that had not changed since the previous release and could be hard-linked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants