feat: gix manifest sourcing #533
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm submitting a
What is the current behaviour?
As of version v0.8.9, Comtrya is no longer able to pull manifests from git sources. This re-introduces it with utilizing gix to resolve issues we had with GitSync and git2-rs with openssl.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
Can fetch and clone a git repo containing comtrya manifests and apply them.
What is the motivation / use case for changing the behavior?
#511
Additional information
That may not be a 100% replacement of older functionality, but I want something out there and that can be tested.
It will not rebase or pull changes after it a repo has been pulled. This is a future update. For now, if you update your repo and need to pull those changes, you can remove the repo that is clones from the "cache_dir" where comtrya places them.
This is a link to the dirt-next documentation with information on the cache dir. We do append to it, but it should be easy to navigate in case you need to clear this would. Go to the cache_dir for your OS and there should be a comtrya folder and drill down from there.
I do hope to over time make a lot of improvements to this.
Please tell us about your environment:
Version (
comtrya --version): mainOperating system: macOS 15.1.1