Regenerate make_blame_rename_tracking_repo archive
#1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Done by running
gix clean -xde
cargo nextest run --workspace --no-fail-fast
on an Ubuntu 25.10 system, and verifying that all tests passed and
that exactly one non-`.gitignore`'d archive was regenerated.
Owner
|
@EliahKagan Thanks a lot, that was very helpful! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This regenerates
make_blame_rename_tracking_repo.tarfor GitoxideLabs#2366.This was done by running
on an Ubuntu 25.10 system, and verifying that all tests passed and that exactly one non-
.gitignore'd archive was regenerated.See GitoxideLabs#2366 (comment) and below for context.
Although I believe I can push directly to this branch (since I have write access on GitoxideLabs/gitoxide, and GitoxideLabs#2366 was opened with the checkbox set to allow maintainers of the target repository to write to the PR branch), I'm opening a "sub-PR" instead. This is in case you prefer to do it some other way, or in case you'd rather investigate whetever was preventing you from regenerating the archive before merging htis.
All CI checks pass on this, which can be verified by inspecting EliahKagan@e9ff5de.