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 adds a cog which determines which directory should be the project root (which is then where the .helix directory is placed), currently based on searching for existing .helix directories, then .jj directories, then .git directories, saving the project root as the first in the current directories parents that contains a .helix, and then if none do the first containing a .jj, ect. If none are found it uses the helix config folder instead of a .helix folder, which will help prevent .helix folders appearing everywhere. There are also functions provided to allow the user to set the project root and helix paths directly.
IMPORTANT: This relies on the parent-name function in my fork of steel, which I've already made a PR adding to steel. (Also this kind of feels like something that should be determined by helix itself rather than a plugin, but it isn't currently so here we are.)