libgit2 / libgit2/rugged

namespace HEAD issue

Open
#488 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
2.3k
Forks
293
PR merge metrics
No merged PRs in 30d

Description

hello, everybody.
here is my bare repo
test_namespace.git$ tree
2015-06-04 18 10 45

cat ./refs/namespaces/A/HEAD
ref: refs/heads/master
irb>require "rugged"
irb>repo=Rugged::Repository.new(".")
irb>repo.namespace="A"
irb>repo.head #=>result is ok

and git-upload-pack failed. here is error msg

~/Code/test/ git clone  git@newgit.com:zouqilin/test_namespace.git
Cloning into 'test_namespace'...
remote: Counting objects: 6, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 6 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (6/6), done.
Checking connectivity... done.
Note: checking out '0f2055ccfb11e0490de20f7c8673b7676981b8bc'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

if i change do as follow.

$> echo "ref: refs/namespaces/A/heads/master"
irb>repo.head# failed
Rugged::ReferenceError: Reference 'refs/namespaces/A/refs/heads/master' not found
    from (irb):5:in `head'
    from (irb):5
    from /usr/local/bin/irb:11:in `<main>'

but git-upload-pack is ok in this case.
so what should i do?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the namespace HEAD behavior with the bare repository, Rugged::Repository#namespace, and repo.head, then compare the two refs/namespaces/A/HEAD contents shown. Check how git-upload-pack resolves each reference and determine the expected behavior for Rugged and Git compatibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, ruby
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.