nextflow-io / nextflow-io/nextflow
nextflow clone does not clone commit hashes
Open
Nobody has claimed this yet.
software/git
triage/investigate
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Bug report
This set of commands:
nextflow drop pipelines/mypipeline
nextflow clone pipelines/mypipeline -hub my_bitbucket -r 0c7ef9be953
Results in an empty directory with the .git sub directory. No error is reported. The same command seems to work well with branches - it seems to be a commit-specific bug. Similar behavior was observed with nextflow pull && nextflow clone commands.
Environment
- Nextflow version:20.10.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported nextflow drop, nextflow clone, and nextflow pull commands with the commit hash, then compare their commit and branch handling. Trace the clone and pull entry points to identify why a commit leaves only .git; done means the requested commit populates the directory and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, groovy
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100