draft articles, providing details about using subprocess run and it's more common inputs and patterns by heckj · Pull Request #347 · swiftlang/swift-subprocess

draft articles, providing details about using subprocess run and it's more common inputs and patterns

heckj

committed

a few tweaks to framing based on some conversations

heckj

committed

the easy updates from initial feedback

heckj

committed

revise the overviews to direct symmetrically based on feedback, and resolving a lingering possessive use

heckj

committed

revising reading and detecting errors into two sections and adding detail and clarity based on initial feedback

heckj

committed

Document run throwing behavior and clarify error terminology

heckj

committed

Update Sources/Subprocess/Documentation.docc/Subprocess.md

heckj

and

invalidname

committed

Update Sources/Subprocess/Documentation.docc/Subprocess.md

heckj

and

invalidname

committed

Apply suggestions from code review

heckj

and

invalidname

committed

applying structural edits to align with guidelines

heckj

committed

more explicit detailing that failure commands aren't errors - to look in terminationStatus, per feedback

heckj

committed

Update Sources/Subprocess/Documentation.docc/GettingStarted.md

heckj

and

invalidname

committed

removing redundant comment/line after API change effect

heckj

committed

Fix DocC symbol links so docs build with warnings-as-errors

heckj

committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

draft articles, providing details about using subprocess run and it's more common inputs and patterns#347

draft articles, providing details about using subprocess run and it's more common inputs and patterns#347
heckj wants to merge 14 commits into
mainfrom
articles

Commits on Jul 14, 2026

draft articles, providing details about using subprocess run and it's more common inputs and patterns

a few tweaks to framing based on some conversations

the easy updates from initial feedback

revise the overviews to direct symmetrically based on feedback, and resolving a lingering possessive use

revising reading and detecting errors into two sections and adding detail and clarity based on initial feedback

Document run throwing behavior and clarify error terminology

Update Sources/Subprocess/Documentation.docc/Subprocess.md

Update Sources/Subprocess/Documentation.docc/Subprocess.md

Apply suggestions from code review

applying structural edits to align with guidelines

more explicit detailing that failure commands aren't errors - to look in terminationStatus, per feedback

Update Sources/Subprocess/Documentation.docc/GettingStarted.md

removing redundant comment/line after API change effect

Fix DocC symbol links so docs build with warnings-as-errors