-
Notifications
You must be signed in to change notification settings - Fork 34
Add workflow: githubnext/agentics/issue-triage #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| # not appropriate for triage workflows, so here we allow one run | ||
| # per issue at a time. | ||
| concurrency: | ||
| group: "triage-${{ github.event.issue.number }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feels like this kind of "pick the right concurrency" should just work. Our compiler should do the right thing and emit a concurrent id with workflow / issue number
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this
concurrency:
group: "triage-${{ github.event.issue.number }}"
is taken directly from actions synteax.
It feels we should introduce some "higher level" syntax for this thing like concurrency: per-issue or concurrency: single and let compiler generate action-specific syntax
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes.... concurrency key has no logging output as far as I know . Very hard to trace.
* Replace check-team-member shared action with inlined JavaScript script (#22) * Initial plan * Replace check-team-member template with inlined JavaScript script Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> * Fix code formatting (remove trailing whitespace) Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> * Add check_team_member.cjs to tsconfig.json and create comprehensive tests Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> Co-authored-by: Peli de Halleux <pelikhan@users.noreply.github.com> * Refactor compute_text_action.yaml as embedded JavaScript with sanitization (#25) * Simplify add-reaction feature by removing fallback and try/catch logic (#24) * Initial plan * Reimplement add-reaction feature as inlined JavaScript Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> * Remove "remove" functionality from add-reaction feature, simplify to only support adding reactions Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> * Remove fallback and try/catch clauses from add-reaction feature Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> Co-authored-by: Peli de Halleux <pelikhan@users.noreply.github.com> * Remove compute-text action dependency and template files from workflow system (#29) * Fix linter issues: Remove unused reactionActionTemplate variable (#30) * Add output text to test-claude and inline JavaScript instead of shared actions (#32) * Remove obsolete reaction_action.yaml template file (#34) * Remove unnecessary content permissions and checkout steps from task and add_reaction jobs (#35) --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Automatically created PR to add workflow: githubnext/agentics/issue-triage