- Notifications
You must be signed in to change notification settings - Fork1k
ci: add workflow for agentic issue triage#19839
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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.
I haven't tested the scripts but looks good and fairly simple. Nice work!
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
| echo "- **Context Key:** ${CONTEXT_KEY}"; | ||
| echo "- **Workspace:** ${WORKSPACE_NAME}"; | ||
| echo "- **Archive URL:** ${ARCHIVE_URL}" | ||
| } >> "${GITHUB_STEP_SUMMARY}" |
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.
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?
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.
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/
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.
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" { ... }| return | ||
| fi | ||
| OPENSSH_CONFIG_FILE="${TEMPDIR}/coder-ssh.config" |
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.
Suggestion: Could setCODER_SSH_CONFIG_FILE instead and avoid passing the flag, but perhaps the more explicit file access is warranted here considering how it's used.
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.
Yep, to the best of my knowledge a--flag will always override an environment variable, hence my usage of a flag instead.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Mathias Fredriksson <mafredri@gmail.com>
thanks I hate it |
1249683 intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
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.