docs: clarify how activation works in practice#5598
Merged
baszalmstra merged 1 commit intoprefix-dev:mainfrom Mar 17, 2026
Merged
docs: clarify how activation works in practice#5598baszalmstra merged 1 commit intoprefix-dev:mainfrom
baszalmstra merged 1 commit intoprefix-dev:mainfrom
Conversation
baszalmstra
approved these changes
Mar 17, 2026
Contributor
|
Thanks! |
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.
Description
Add basic examples of
pixi shell-hookusage since those seemed to be missing so far and make it clear thatpixi shellshould never be put in a shell's startup file.Fixes part of #5510.
Note: theare are also other documents touching on activation, like https://pixi.prefix.dev/latest/workspace/environment/#activation and https://pixi.prefix.dev/latest/advanced/pixi_shell/, but I left those as-is because imo this basic yet important information should be put where it is most likely to be looked for i.e. next to the command's own explanation.
On the other hand something like https://pixi.prefix.dev/latest/advanced/pixi_shell/#issues-with-pixi-shell is almost about the exact same change I made in shell.md so please advise if this needs to be structured in a different way.
Perhaps simply linking directly to the relevant .md files in the aformentiond links would already help? It's a bit weird to have a page dedicated to
shellwithout actually linking to its core documentation?How Has This Been Tested?
I only looked at the docs in a markdown previewer: don't know how else to check.