Submodules disappears when checking out a revision

Open
#900 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at Rugged's repo.checkout API and the documented recursive submodule option, using the origin/<branch_name> example as the reproduction. Determine how checkout currently handles submodules and define completion as recursively checking out submodules with the same options, with behavior verified for a project containing several submodules.

Written by the indexing model from the issue text.

Description

I have a git project that has several submodules, if I checkout a specific version:

repo.checkout("origin/#{branch_name}", {strategy: :force})

the submodules folder is empty and it seems I can't checkout the submodules in any way.

I see that checkout should have an option
Recursively checkout submodules with same options (NOT IMPLEMENTED).

but it is not working because it is not implemented. Anyway I can checkout also the submodules through the Rugged Library?

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

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.

More from libgit2/rugged

All issues in libgit2/rugged

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.