Skip to content

Conversation

@moskyb
Copy link
Contributor

@moskyb moskyb commented Jan 2, 2026

Description

I was in this code investigating an escalation, and found it quite hard to parse out what was going on, so i did a couple of light refactors to make it a little easier to follow. It stops the envar generation process from reparsing lists of envars, and generally shuffles things around a wee bit.

This PR is fairly low-value, and at best has no impact on the agent at runtime. I'm happy to close it and move on with my life, if we want.

Testing

  • Tests have run locally (with go test ./...). Buildkite employees may check this if the pipeline has run automatically.
  • Code is formatted (with go tool gofumpt -extra -w .)

Disclosures / Credits

There was a wee bit of Amp (Claude Opus 4.5) involved in minor refactors, name choosing etc.

@moskyb moskyb requested a review from a team January 2, 2026 05:46
Copy link
Contributor

@zhming0 zhming0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, much easier to read! I wonder if we can just have one tiny e2e test case that uses some plugin? just so this code path is test covered.

I was in this code investigating an escalation, and found it quite hard to parse out what was going on, so i did a couple of light refactors to make it a little easier to follow
@moskyb moskyb force-pushed the refactor-plugin-envar-generation branch from 53cc8c9 to 52d8601 Compare January 9, 2026 02:49
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.

3 participants