jacebrowning / jacebrowning/gitman
Feature request: Equivalent of git push --recurse-submodules=check to verify submodules have no unpushed or uncommitted changes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 225
- Forks
- 36
- Avg merge
- 15h 47m
- Merged PRs (30d)
- 8
Description
Is there a way in Gitman to verify that all submodules (gitman.yml dependencies) are fully pushed and consistent with their remotes, similar to git push --recurse-submodules=check?
It would be useful to have a command like "gitman subrepo check" returning 0/1 exit code for scripting pre-push hooks.
Reference: "Git Submodules - Publishing" (https://git-scm.com/book/en/v2/Git-Tools-Submodules#_publishing_submodules)
Read attached file for full explanation.
[full-issue-text.md](https://github.com/user-attachments/files/22857951/full-issue-text.md)
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 reading the command entry points for Gitman and how dependencies from gitman.yml are inspected. Investigate the requested `gitman subrepo check` behavior against Git's submodule publishing guidance, including unpushed and uncommitted changes. Done means the command returns the documented success or failure exit code for scripting and pre-push hooks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100