Repository navigation
chore(agent-loop): deploy the engineering agent loop's workflows that call no model - #58
Merged
Merged
Conversation
lis365b
approved these changes
Nov 11, 2026
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.
What changes
13 files, all under
.github/, no product code.+403 / −3,204.This repository is public, and the files being removed are the ones that run an AI agent. They read their instructions from a private repository, which a public one cannot fetch, so they could never have run here. What stays is the workflows that do their work on their own.
.github/aw/imports/dlt-hub/engineering-agent-loop/27ad2f9…/(deleted).github/aw/imports/.gitattributes(deleted).github/workflows/review.mddescribes the workflow (deleted).lock.ymlfile is the same workflow generated for GitHub to run (deleted).release-changelog.cjsmoves what## [Unreleased]has collected under a version heading, and reads that section back as the release body.release-dlthub-init.ymlmoves the package version and cuts the changelog when somebody asks it to, and creates the GitHub release once that pull request merges.bump-dlthub-init.ymlwatches PyPI for adlt,dlthubordlthub-clientrelease, runs this repository's own bump recipe when one lands, and opens the pull request for it (modified).report-failure.ymlsays on an issue or pull request that a run working on it did not finish, in the cases where the run itself could not (deleted).start-feedback.ymlstartsreviewwhen a reviewer requests a change on one of those pull requests, or comments on a line of it (deleted)..gitattributesmarks the generated files as generated, so they collapse in a diff (deleted).