VisionSystemsInc / VisionSystemsInc/vsi_common
Submodule update on windows
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8
- Forks
- 9
- Avg merge
- 36m
- Merged PRs (30d)
- 1
Description
Updating the vsi_common submodule from just on windows, will cause git to error if it tries to rewrite the just file itself, as it is in use, and Windows doesn't support this like *nix does.
The result is a horrible explosion of a partially checked out vsi_common repo, in a dirty state, that takes both a git reset --hard and git clean df, followed by a manual update.
Possible solutions:
- Someway to detangle using the
justfile on windows, an exec to a tmp file?setup.envcould define the functionjustinstead, that would source what is currently the file just
- git hook on windows, to keep vsi_common up to date...
- Detecting the problem before it happens, and echoing out that you need to
git submodule update --recursive vsi_commonmanually
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by inspecting the just file and setup.env, then reproduce the Windows submodule update path involving git. Done means updating vsi_common on Windows no longer leaves a partially checked-out dirty repository, or detects the condition and clearly directs the manual recursive update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100