fix: respect CORTEX_HOME in alias command#261
Open
mi6886 wants to merge 1 commit into
Open
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.
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
1 participant
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.
Fixes PlatformNetwork/bounty-challenge#51514.
This updates the alias command to use the shared Cortex home resolver before appending
aliases.toml, so alias reads and writes honor the activeCORTEX_HOME.Changes:
cortex_common::get_cortex_home()for alias config path resolution.~/.cortex/aliases.tomlfallback when common directory resolution is unavailable.CORTEX_HOMEis respected.Verification:
git diff --checkNote: I could not run the focused Rust tests locally because this environment does not currently have
cargoorrustfmtinstalled in PATH.