[docs] Update documentation for --push flag feature (PR #8971) #9020
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.
Documentation Updates - January 5, 2026
This PR updates the documentation based on the new
--pushflag feature merged in the last 24 hours.Feature Documented
--pushflag forgh aw runcommand (from PR #8971)The
--pushflag provides an all-in-one workflow update and execution experience:.lock.ymlfiles.mdand.lock.ymlfiles plus dependencies--refflagChanges Made
Updated
docs/src/content/docs/setup/cli.md:--pushand--refoptions to theruncommand documentation section--pushflag functionality with 7 key features--pushexample--pushusage patternsUsage Examples
Merged PRs Referenced
Analysis Summary
Reviewed 30+ merged PRs from the last 24 hours. Most were internal refactoring, security fixes, or bug fixes that don't require user-facing documentation updates. PR #8956 (hourly schedule feature) was already documented in its own PR.
The
--pushflag is a significant user-facing feature that simplifies the workflow development cycle and was missing from the CLI documentation.Documentation Standards
This update follows project documentation guidelines: