Open
Conversation
We use this to cache git repos that contain our justfiles, so that we can import them.
|
Fetching recipes from remote resource over the internet was already discussed at this post. In short right now the community does not want to handle network related stuff. This git functionality is however network stuff. Sharing just file through a remote Git repository can be also be archived by writing a just recipe invoking git commands to clone/get the recipe into the local project directory of a user. Shared repository could be managed as git sub-modules in one's project. |
|
My plan is to solve such use-cases with wildcard support. |
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.
This is probably a bad idea because it introduces the concept of dependencies, which
justis blissfully devoid of currently.However, I really wanted teams to have the ability to link to a shared set of functions or tasks that could help keep our Just files in each repo no only shorter, but also more consistent between projects, without lots of copy and paste.
My thinking was the easiest way to do that is to have
justclone repositories into a local cache, and handle versioning by using the sha1 in the import path of the git repository to check out specifically that version, but to otherwise default to the current HEAD of the repository.Rust is not a primary language for me, so feel free to ask for changes or close this PR.
I just wondered if something in this area was interesting to anybody else.