Repository navigation
Triage request: jctanner #8776
Closed
jctanner
started this conversation in
Triage Request
Replies: 1 comment
|
approve |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Contribution history
Merged PRs — fullsend-ai/strat-creator (17):
Open PRs — fullsend-ai/strat-creator:
iterating through review, 21 comments so far)
fullsend-ai/fullsend:
(PR fix(hooks)!: resolve the hook interpreter and hook PATH from directories the agent cannot write #8605). Restructured per maintainer review into a rules-based
Decision with a per-runtime conformance table; iterating on feedback.
review (gsun: "this bypass entrypoint solution is not good"). I
accepted the rejection and the boundary it established is now a
documented non-goal — the follow-up work (fullsend#8202, and the workflow-
definitions direction of fullsend#8225) stays on the agent-led path.
Reviews: I review with parallel independent model passes and
cross-check findings before posting (e.g., the dual-model review rounds
on my own ADR revisions, and review participation in the strat-creator
#85 and fullsend
#7947/#8751
Why do you need triage access?
I'm part of the ADLC team and would like to have the ability to run /fs-review as part of my daily work.
Checklist
All reactions