[go: nahoru, domu]

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

Pull workflow.revision into config scopes #3133

Open
tjdurant opened this issue Aug 22, 2022 · 4 comments · May be fixed by #3651
Open

Pull workflow.revision into config scopes #3133

tjdurant opened this issue Aug 22, 2022 · 4 comments · May be fixed by #3651

Comments

@tjdurant
Copy link

Usage scenario

Currently, we prefer to run our pipeline with a nextflow run command that points to a private GitLab repo and a specific release tag:

nextflow run <git_repo_url> -r <tag>

We also like to put the pipeline output files in a directory that has the pipeline tag/version in the path:

~/PIPELINE_OUTPUT_v1.3.0/path/to/files

We think it would be useful to have a feature that allows users to pull workflow.revision into config files where those output paths are defined.

More information/details on this request in Discussion #3130

Happy to add additional details as needed.

Thanks!
Tom

@stale
Copy link
stale bot commented Jan 21, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 21, 2023
@tjdurant
Copy link
Author

I think this would still be a good feature to have.

@stale stale bot removed the stale label Jan 23, 2023
@stale
Copy link
stale bot commented Aug 12, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@bentsherman
Copy link
Member

Should be solved by #3651, check that PR and let me know if it covers the config options you're interested in.

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

Successfully merging a pull request may close this issue.

2 participants