nextflow-io/nextflow

nextflow clone does not clone commit hashes

Open

#1,987 opened on Mar 24, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Groovy (784 forks)batch import
help wantedsoftware/git

Repository metrics

Stars
 (3,382 stars)
PR merge metrics
 (Avg merge 16d 9h) (54 merged PRs in 30d)

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

Research direction
Investigate the clone command implementation in Nextflow, focusing on how it handles commit hashes vs branches. Check the git clone command construction and ensure the commit hash is correctly passed.
Tech stack
None
Domain
clibackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70