On https://pixi.prefix.dev/dev/workspace/lockfile , searching for "commit" yields no results.

It would be great to have a documentation about whether to commit the lockfile in git - this should be both from the perspective of working with application code as well as from a library author perspective.

If the recommendation for library authors requires complex CI to set up, I think that there should:

• (if applicable) be further development within the Pixi ecosystem to ease these ergonomics and simplify the process (e.g, creating a bot to help with PRs), and (until this is done)
• be an alternate recommendation (e.g., ignore the lock file ) with clearly documented downsides so that smaller libraries don't have to deal with this complex setup

Related documentation/context:

• GitHub action to help users (who gitignored their lockfile) save CI time: https://github.com/Parcels-code/pixi-lock#why-not-commit-the-lock-file
• discussion in prefix Discord about said action https://discord.com/channels/1082332781146800168/1462778624212996209