Offline Git collection: isolate inherited repository context and credential environment
Maintainers usually reply within 9 days
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start with the local Git subprocess and synthetic fixture command setup, then inspect the offline replay and source proof checks. Reproduce the regression by selecting repository A while GIT_DIR and GIT_WORK_TREE point to B, and verify the resulting commit remains in A and subprocess environments omit those overrides and a credential sentinel. The issue says the fix is already implemented in pending release 0.6.0 and linked to PR #75; it asks to retain the issue until that PR merges.
Written by the indexing model from the issue text.
Description
Native local Git reads must use the repository selected by --repo, independent of inherited GIT_DIR/GIT_WORK_TREE/config injection. Local offline subprocesses also have no need for unrelated credential environment variables.
During full-suite verification, subprocess fixture failures showed why forwarding the complete parent environment makes diagnostics needlessly sensitive. No credentials belong in a public fixture or CI artifact.
Fix: allowlist the OS/path/home/locale variables needed by local Git, add explicit no-lazy-fetch/prompt/optional-lock controls, and omit inherited Git context and credential variables. Synthetic fixture commands similarly isolate their environment and user/system configuration.
Regression: select repository A with inherited GIT_DIR/GIT_WORK_TREE pointing at unrelated B; prove the resulting commit remains A and all subprocess environments omit both the override and a synthetic credential sentinel. Existing source proof and offline replay still pass.
Related: #72. Implemented in the pending 0.6.0 release; retain the issue until the fixing PR merges.
- Dominant language
- Python
- Stars
- 4
- Forks
- 1
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from drevendev/Devostasis
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
drevendev/Devostasis#25 ·
Maintainers usually reply within 9 days
-
good first issue hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 56/100
drevendev/Devostasis#78 ·
Maintainers usually reply within 9 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
drevendev/Devostasis#77 ·
Maintainers usually reply within 9 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
drevendev/Devostasis#76 ·
Maintainers usually reply within 9 days
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
drevendev/Devostasis#73 ·
Maintainers usually reply within 9 days
All issues in drevendev/Devostasis
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
mihai-vlc/sublime-jsfmt#56 ·
-
comp/cli comp/plugins P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NousResearch/hermes-agent#141917 · 1 comment ·
Maintainers usually reply within 1 day
-
Go device SDK: Whisper transcriber keeps buffering and transcribing audio appended after Stop()Possibly taken @apoorvdarshan claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#22770 ·
Maintainers usually reply within 1 day
-
bug needs-acceptance wg/router-models-inference-runtime
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
vllm-project/semantic-router#5295 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
huggingface/huggingface_hub#5210 ·
Maintainers usually reply within 1 day