Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a new agent pipeline for automatically fixing CI failures. The CI agent works in a similar way to the GitHub agent but is triggered by CI failures rather than GitHub issues.
Changes Made
Created new CI-specific components:
CIOutputParser: Parses CI output logs into Haystack documentsCIBranchCreator: Creates a new branch for fixing CI issuesCIDocumentToChatMessageConverter: Converts CI failures into structured chat messagesImplemented a CI agent pipeline:
ci_agent.pypipeline similar to the GitHub agent but adapted for CI inputAdded a GitHub workflow:
ai_ci_processor.yamlworkflow that runs on CI failureImplementation Details
The CI agent has the same core functionality as the GitHub agent but uses different input sources and parsing mechanisms:
fix-ci-1234567890)Testing Considerations
To test this implementation:
Next Steps
Closes #17