8000 chore(agent-loop): update the engineering agent loop to 059f1e2 by engineering-agent-loop-deploy[bot] · Pull Request #57 · dlt-hub/dlthub-init · GitHub
[go: up one dir, main page]

Skip to content

chore(agent-loop): update the engineering agent loop to 059f1e2 - #57

Closed
engineering-agent-loop-deploy[bot] wants to merge 1 commit into
develfrom
deploy/review-059f1e2-42607676400
Closed

engineering-agent-loop-deploy[bot] wants to merge 1 commit into
develfrom
deploy/review-059f1e2-42607676400

Conversation

@engineering-agent-loop-deploy
Copy link
Copy Markdown
Contributor
  • Moves the engineering agent loop here from 27ad2f9 to 059f1e2 (what changed).
  • Quick summary of the loop: review reviews and repairs it, then requests a reviewer.
  • The loop cannot merge.

What changes

8 files, all under .github/, no product code. +449 / −56.

Files What they are
.github/aw/imports/dlt-hub/engineering-agent-loop/059f1e2…/ the instructions the agent is given, read off disk at the start of a run

.github/workflows/

  • review.md describes the workflow (modified)
  • The .lock.yml file is the same workflow generated for GitHub to run (modified).
  • release-changelog.cjs moves what ## [Unreleased] has collected under a version heading, and reads that section back as the release body.
  • release-dlthub-init.yml moves the package version and cuts the changelog when somebody asks it to, and creates the GitHub release once that pull request merges.

The loop's scripts, rules and profiles stay in its own repository and are fetched at run time.

@lis365b
lis365b commented Nov 9, 2026
Copy link
Copy Markdown
Contributor

Superseded by #58, which stops deploying the agent workflow files here entirely. See dlt-hub/engineering-agent-loop#480.

@lis365b lis365b closed this Nov 9, 2026
@lis365b
lis365b deleted the deploy/review-059f1e2-42607676400 branch November 9, 2026 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0