Repository navigation
[product-manager-impersonator] Quick setup --allow-dirty mode #995
Description
Feature Idea
Summary: Add an optional --allow-dirty flag to scripts/quick-setup.sh so first-time setup can run in repos that already have local uncommitted changes.
Why a Customer Would Want This
Many teams try quick setup while already in the middle of unrelated local edits. The current hard stop forces them to stash/commit first, which adds friction and often delays adoption. An explicit opt-in keeps the safe default while unblocking real-world onboarding flow.
Rough Implementation Sketch
- Add
--allow-dirtytoscripts/quick-setup.shusage/help and argument parsing. - Keep current behavior as default; only bypass the dirty-tree exit when this flag is set.
- In
--allow-dirtymode, create/switch branch from currentHEAD(instead of requiring clean checkout from default branch) and print a clear warning that the branch may include pre-existing changes. - Continue staging/committing only generated workflow files (
created_files) and document the new flag in README + workflow setup docs.
Why It Won't Be That Hard
This is a small, localized shell-script enhancement with no workflow schema/compiler changes. The script already has centralized option parsing and already limits commits to generated files, so the change is mostly conditional branching plus docs updates.
Evidence
- Current hard stop on dirty worktree:
scripts/quick-setup.sh#L90-L93. - Default branch checkout path that assumes clean state:
scripts/quick-setup.sh#L173-L183. - Commit scope already constrained to generated files:
scripts/quick-setup.sh#L186-L213andscripts/quick-setup.sh#L261-L266. - Quick setup is a primary onboarding path in docs:
README.md#L28-L39,gh-agent-workflows/README.md#L44-L65. - Recent activity shows active investment in quick-setup usability text and onboarding polish: issue
#990, PR#991, and commited04d2351df4c732fb9f2c2aa42a3d2a8d991494.
Duplicate Check
repo:elastic/ai-github-actions is:issue is:open "allow-dirty" OR "allow dirty" "quick-setup"→ no open match.repo:elastic/ai-github-actions is:issue is:open "Working tree has uncommitted changes"→ no open match.repo:elastic/ai-github-actions is:issue is:open "quick-setup" "uncommitted"→ no open match.- Reviewed
/tmp/previous-findings.json: many quick-setup ideas exist (labels bootstrap, defaults file, safety checks, list/validate modes), but none propose dirty-worktree opt-in setup.
Note
🔒 Integrity filter blocked 21 items
The following items were blocked because they don't meet the GitHub integrity level.
- #937
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #851
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #850
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #794
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #359
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #704
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #505
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #476
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Create issue when merged PRs had unresolved comments #875
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Add PR Docs Review workflow #704
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Add target-repo support to scheduled workflows #694
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Shorter replies from pr-actions-detective #684
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Detector / Fixer chaining workaround #676
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #694
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #684
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #875
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - ... and 5 more items
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools:
github:
min-integrity: approved # merged | approved | unapproved | noneWhat is this? | From workflow: Trigger Product Manager Impersonator
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Activity