Skip to content

ci: add workflow for agentic issue triage#19839

Merged
johnstcn merged 23 commits into
mainfrom
cj/hack/traiage
Sep 22, 2025
Merged

ci: add workflow for agentic issue triage#19839
johnstcn merged 23 commits into
mainfrom
cj/hack/traiage

Conversation

@johnstcn
Copy link
Copy Markdown
Member

@johnstcn johnstcn commented Sep 16, 2025

Adds a GH workflow to start a workspace with a pre-determined template, perform a first pass over a given GitHub issue, and persist the changes in a GCS bucket for later refining. Tested locally with nektos/act.

Note: "traiage" is not a typo.

@johnstcn johnstcn self-assigned this Sep 16, 2025
@johnstcn johnstcn changed the title [WIP] add workflow for agentic issue triage ci: add workflow for agentic issue triage Sep 18, 2025
@johnstcn johnstcn marked this pull request as ready for review September 18, 2025 18:44
Copy link
Copy Markdown
Member

@mafredri mafredri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't tested the scripts but looks good and fairly simple. Nice work!

Comment thread .github/workflows/traiage.yaml Outdated
Comment thread .github/workflows/traiage.yaml Outdated
Comment thread .github/workflows/traiage.yaml
echo "- **Context Key:** ${CONTEXT_KEY}";
echo "- **Workspace:** ${WORKSPACE_NAME}";
echo "- **Archive URL:** ${ARCHIVE_URL}"
} >> "${GITHUB_STEP_SUMMARY}"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we also output here how to utilize the artifact?

PS. What's the difference of throwing it into step summary vs just outputting to stdout?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GITHUB_STEP_SUMMARY will let you emit markdown that's visible in the job execution log

ref: https://github.blog/news-insights/product-news/supercharging-github-actions-with-job-summaries/

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the "how-to" -- I think we will want to add some level of automation around this in the associated template. Something like the below:

data "coder_parameter" "resume_context_key" {
  name = "resume_context_key"
  type = "string"
  default = ""
}

locals {
  archive_url = "gs://${var.gcp_bucket}/traiage/${context_key}"
}

resource "coder_script" "fetch_context" { ... }

Comment thread scripts/traiage.sh
return
fi

OPENSSH_CONFIG_FILE="${TEMPDIR}/coder-ssh.config"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Could set CODER_SSH_CONFIG_FILE instead and avoid passing the flag, but perhaps the more explicit file access is warranted here considering how it's used.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, to the best of my knowledge a --flag will always override an environment variable, hence my usage of a flag instead.

Comment thread scripts/traiage.sh Outdated
Comment thread scripts/traiage.sh Outdated
Comment thread scripts/traiage.sh Outdated
Comment thread scripts/traiage.sh Outdated
Comment thread scripts/traiage.sh Outdated
johnstcn and others added 3 commits September 19, 2025 17:05
Co-authored-by: Mathias Fredriksson <mafredri@gmail.com>
@aslilac
Copy link
Copy Markdown
Member

aslilac commented Sep 19, 2025

Note: "traiage" is not a typo.

thanks I hate it

@johnstcn johnstcn merged commit 1249683 into main Sep 22, 2025
46 of 48 checks passed
@johnstcn johnstcn deleted the cj/hack/traiage branch September 22, 2025 12:29
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants