Skip to content

bender clone tmp tag #256

Open
Open

Description

@sigmuha

When using bender clone <PKG>, the checked-out repository uses a temporary bender tag. Is there a reason for this?

I would believe most users will change the branch to the specific tag/branch they are working from anyway, so is there a reason for creating tags for these repos, when Bender won't touch them?

A solution is to drop creating this tag and just check out the tag/rev in the manifest.

Activity

  1. micprog commented on Feb 24, 2026

    @micprog
    Member

    Bender aims to check out the commit hash specified in the Bender.lock to ensure consistency and reproducibility of a project. To do this, bender internally clones a bare repository in the db directory. Within this, it creates a temporary tag to clone to the project directory because git clone <hash> does not work. See https://github.com/pulp-platform/bender/blob/master/src/sess.rs#L975-L977 for more details.
    To work on a working branch for a specific dependency, I suggest utilizing the bender clone <dep> and bender snapshot (and finally bender update) mechanics (described here).

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions