You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d777b2f
Browse filesBrowse the repository at this point in the historyBrowse files
test: isolate repository fixtures from checkout history
Took a quick look, pretty zoomed out, but think it's
a desirable change as finally the test-suite is independent
of the input repository or state.
<!-- agent -->
Make PR and post-merge test results independent of checkout depth, refs,
and history. The shared test repository and dependency clone sources
previously came from the source checkout, requiring historical objects
and a bootstrap script even though setup already used `gix.testtools`.
Generate small repositories from scratch through `gix.testtools`, with
named root, release, merge, conflict, rename, date, and submodule states.
Adapt legacy assertions to those scenarios while retaining merge,
serialization, traversal, index, remote, and nested-submodule coverage.
Make dirty-submodule removal checks explicit for staged, unstaged, and
untracked data, including dry runs.
Remove the source-history environment override, dependency factory,
checkout lock cleanup, and bootstrap script. The main CI suites now use
shallow checkouts and remove source `.git` metadata before pytest. Add a
regression that initializes the shared fixture from a source copy without
Git metadata, and document the isolation requirement. Hash raw parser
samples in cache arguments to avoid archive filename limits on cold runs.
Assisted-by: GPT 6.0 Astra
Co-authored-by: GPT 6.0 Astra <codex@openai.com>
On Windows, `./init-tests-after-clone.sh` can be run in a Git Bash shell.
125
-
126
123
If you are cloning [your own fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks), then replace the above `git clone` command with one that gives the URL of your fork. Or use this [`gh`](https://cli.github.com/) command (assuming you have `gh` and your fork is called `GitPython`):
127
124
128
125
```sh
@@ -175,9 +172,8 @@ See [Issue #525](https://github.com/gitpython-developers/GitPython/issues/525).
175
172
176
173
### RUNNING TESTS
177
174
178
-
_Important_: Right after cloning this repository, please be sure to have executed
179
-
the `./init-tests-after-clone.sh` script in the repository root. Otherwise
180
-
you will encounter test failures.
175
+
Test repositories are generated from scratch by fixture scripts. Tests work from
176
+
a shallow clone or a source copy without `.git`; no checkout preparation is needed.
0 commit comments