You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary: Add an opt-in --auto-stash flag to scripts/quick-setup.sh so setup can proceed when the repository has local uncommitted changes.
Why a Customer Would Want This
Teams often try quick setup while actively working in a repo. Today setup hard-fails on any dirty working tree, which interrupts onboarding and adds manual stash/commit steps before users can even try the workflows.
Rough Implementation Sketch
Add --auto-stash to scripts/quick-setup.sh argument parsing and help text.
Keep current behavior as default; only stash when the flag is explicitly set.
On dirty tree + --auto-stash, run a labeled stash (including untracked files), continue setup, and print explicit restore instructions at the end.
Document the new flag in quick-setup docs (README.md and gh-agent-workflows/README.md).
Why It Won't Be That Hard
The script already has a single, centralized dirty-tree gate and a linear setup flow. This feature is an additive branch around existing logic in one script plus small docs updates, with no new services or architecture changes.
Evidence
scripts/quick-setup.sh:90-93 currently exits immediately on any uncommitted changes.
scripts/quick-setup.sh:23-30 lists supported flags; there is no dirty-tree override path.
scripts/quick-setup.sh:177-182 always checks out/creates the setup branch, so users currently must clean/stash manually first.
README.md:28-39 presents quick setup as a single command onboarding path.
gh-agent-workflows/README.md:44-65 documents quick setup options but no way to proceed from a dirty tree.
Recent feature ideas and open issues include many quick-setup improvements, but none covering auto-stash for uncommitted changes (checked issue search and previous findings list).
Note
🔒 Integrity filter blocked 37 items
The following items were blocked because they don't meet the GitHub integrity level.
#1175list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#359search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#1067search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#704search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#694search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#684search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#875search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#676search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#505search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#476search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
Mint Ephemeral Tokens #1067list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
Feature Idea
Summary: Add an opt-in
--auto-stashflag toscripts/quick-setup.shso setup can proceed when the repository has local uncommitted changes.Why a Customer Would Want This
Teams often try quick setup while actively working in a repo. Today setup hard-fails on any dirty working tree, which interrupts onboarding and adds manual stash/commit steps before users can even try the workflows.
Rough Implementation Sketch
--auto-stashtoscripts/quick-setup.shargument parsing and help text.--auto-stash, run a labeled stash (including untracked files), continue setup, and print explicit restore instructions at the end.README.mdandgh-agent-workflows/README.md).Why It Won't Be That Hard
The script already has a single, centralized dirty-tree gate and a linear setup flow. This feature is an additive branch around existing logic in one script plus small docs updates, with no new services or architecture changes.
Evidence
scripts/quick-setup.sh:90-93currently exits immediately on any uncommitted changes.scripts/quick-setup.sh:23-30lists supported flags; there is no dirty-tree override path.scripts/quick-setup.sh:177-182always checks out/creates the setup branch, so users currently must clean/stash manually first.README.md:28-39presents quick setup as a single command onboarding path.gh-agent-workflows/README.md:44-65documents quick setup options but no way to proceed from a dirty tree.Note
🔒 Integrity filter blocked 37 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Trigger Product Manager Impersonator
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.