chore: apply changes for Issue #223 #224
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #223
Applied changes based on Issue #223.
I’ve added end-to-end support for a new
--fix-buildflag:• Parsing the flag
–
processEventnow recognizes--fix-buildboth in issue/PR comments and in thedirect-promptinput.– Added an
includeFixBuild: booleanfield to theProcessedEventinterface.• Fetching the latest failure logs
– Introduced
fetchLatestFailedWorkflowLogs(octokit, repo)which uses the GitHub Actions API to find the most recent failed run and returns its logs URL (or an error message).• Injecting logs into the prompt
– In
runAction, ifincludeFixBuildis true, we pull in those logs and build a prompt like:“Latest failed build logs: …Please suggest changes to fix the build errors above.”
– This prompt then flows through
generatePrompt→runCodexand results in an automated PR to fix the build.• Tests updated
– The direct-prompt and issues-assigned unit tests now expect
includeFixBuild: falsewhen not using the new flag.Let me know if you’d like to tweak how much of the logs is passed (e.g. full text extraction vs. just the URL) or adjust the prompt wording!