Lineage - explicitly note that paths can be remote#6819
Draft
Lineage - explicitly note that paths can be remote#6819
Conversation
Signed-off-by: Phil Ewels <phil.ewels@seqera.io>
ewels
force-pushed
the
lineage-bucket-docs
branch
from
a370fba to
24a70d7
Compare
❌ Deploy Preview for nextflow-docs-staging failed. Why did it fail? →
|
✅ Deploy Preview for nextflow-docs-staging canceled.
|
Member
Author
|
Comments from Slack:
|
Signed-off-by: Chris Hakkaart <chris.hakkaart@seqera.io>
christopher-hakkaart
approved these changes
Feb 16, 2026
Collaborator
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
There was a problem hiding this comment.
Made one small editorial change and merged it. Looks good otherwise.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
No description provided.