Skip to content

feat: rewrite customizing environments #243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 10, 2025
Merged

Conversation

zmitchell
Copy link
Member

This previously focused exclusively on shell hooks and used them to run a service. This now shows a user how to leverage the hook, profile, and vars sections to customize their shell environment in an activated environment.

@zmitchell zmitchell force-pushed the push-yuzzmytxyxxq branch from b79b446 to d2e9bfb Compare June 9, 2025 23:45
Copy link

github-actions bot commented Jun 9, 2025

Copy link
Contributor

@jennymahmoudi jennymahmoudi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice focus on the user's goals! Left some minor suggestions but no major changes, so I'm approving now. 👍

```
The logic for deciding where a customization should go is application specific, but there are some simple guidelines you can follow.
For a full discussion of what logic to place in which section and why, see the [activation concept page][activation_concept].
Otherwise, try this:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of logic to explain this but I don't think the bulleted list format is working here. Perhaps it's just that the indentation didn't work as you intended?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh that definitely got mangled

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So our linter yells at me if the indentation is 4 spaces, but it renders properly. It doesn't yell at you if you use 2 spaces, but then it doesn't render properly 🫠

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed this by ignoring the linter. I also added a lint shell alias to the environment so you can check this kind of thing locally without needing to remember that the name of the command is actually markdownlint-cli2.

@zmitchell zmitchell force-pushed the push-yuzzmytxyxxq branch from d2e9bfb to db6d1cf Compare June 10, 2025 21:09
Copy link

This previously focused exclusively on shell hooks and used them to run
a service. This now shows a user how to leverage the hook, profile, and
vars sections to customize their shell environment in an activated
environment.
@zmitchell zmitchell force-pushed the push-yuzzmytxyxxq branch from db6d1cf to 95d5af3 Compare June 10, 2025 21:13
Copy link

@zmitchell zmitchell merged commit 4c76cf0 into preview Jun 10, 2025
3 checks passed
@zmitchell zmitchell deleted the push-yuzzmytxyxxq branch June 10, 2025 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants