Document VIPM_NONINTERACTIVE env var and CI auto-detection#61
Merged
Conversation
VIPM now auto-enables non-interactive mode in CI environments, preventing commands from hanging on missing input. This updates the docs to reflect the new behavior and the VIPM_NONINTERACTIVE env var that controls it. - Add VIPM_NONINTERACTIVE section with behavior table, precedence rules, and usage examples to the environment variables reference - Correct CI detection note (previously said "affects timeouts only") - Update GitHub Actions and Docker guides to explain auto-detection - Add env var cross-references to --yes flag in command reference - Add VIPM_NONINTERACTIVE to 2026.3 release notes
Contributor
|
…or reproducible builds
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.
Summary
VIPM now auto-enables non-interactive mode in CI environments, preventing commands from hanging on missing input. The existing docs incorrectly stated that CI detection "affects timeouts only" — it now also controls prompt behavior. These changes document the
VIPM_NONINTERACTIVEenv var and update all CI/automation guides to reflect the new behavior.VIPM_NONINTERACTIVEsection with behavior table, precedence rules, and usage examples; corrected CI detection note; restructuredVIPM_ASSUME_YESas a subsection under the new Non-Interactive Mode heading--yesconfiguration.envexample to useVIPM_NONINTERACTIVE=1; updated tip to distinguish standalone Docker from CI-hosted containers--yesflag descriptions for install and uninstallVIPM_NONINTERACTIVEto the env vars list; updated CI detection bulletTest plan
#vipm_noninteractiveanchor)