chore: Update default pixi gitignore and gitattributes #1488
Conversation
This file contains 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
ruben-arts
reviewed
Jun 8, 2024
|
The diff thing is awesome! |
pavelzw
commented
Jun 10, 2024
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.
With.pixi/config.tomlbeing a valid configuration place, what do you think about excluding it from .gitignore?Also, with pixi.lock file diffs getting very large, especially with multi-envs, I think it makes sense to add
linguist-generated=true(in some cases, github refused to render the markdown anyway). https://github.com/pavelzw/pixi-diff-to-markdown can generate a bit prettier diffs anyway.Maybe it makes sense to have a diff mode
pixi diff pixi.lock.old pixi.lock.newas well that generates the same json output aspixi update --jsonand allow people to configure their git diff to use pixi similar to how bun does it.