git: enable subprocessing by default #5652
Merged
Conversation
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
Given the previously‐stated intention of making this default for the 0.27 release, prepare for that decision ahead of time by enabling subprocessing by default on trunk. This will help surface any regressions and workflow incompatibilities and therefore give us more information to decide whether to keep or revert this commit, without inconveniencing any users who haven’t already opted in to the bleeding edge. Please feel free to revert without hesitation if any major issues arise; this is not intended as a strong commitment to enable this option for the next stable release if it turns out to not be ready. In that case, it’s better that we learn that early on in the cycle, rather than having to revert at the last minute or, worse, cutting a stable release that we later find contains a serious regression.
martinvonz
approved these changes
Feb 10, 2025
bsdinis
approved these changes
Feb 10, 2025
11 tasks
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.
Given the previously‐stated intention of making this default for the 0.27 release, prepare for that decision ahead of time by enabling subprocessing by default on trunk. This will help surface any regressions and workflow incompatibilities and therefore give us more information to decide whether to keep or revert this commit, without inconveniencing any users who haven’t already opted in to the bleeding edge.
Please feel free to revert without hesitation if any major issues arise; this is not intended as a strong commitment to enable this option for the next stable release if it turns out to not be ready. In that case, it’s better that we learn that early on in the cycle, rather than having to revert at the last minute or, worse, cutting a stable release that we later find contains a serious regression.
Checklist
If applicable:
CHANGELOG.md