"AutoBuilder - Failed" issues should be left open

Open
#2,085 0 comments 1 reaction 2 assignees View on GitHub

@lbussell is already working on this.

Since Apr 20, 2026.

  • #2093 by @copilot-swe-agent — open

Assessment

This issue has not been assessed yet.

Description

area-infrastructure

Currently, NotificationService immediately closes any issue that does not have the failure label:

https://github.com/dotnet/docker-tools/blob/78513bb41bc2a907b161c6e13cd0699b5252c5d9/src/ImageBuilder/NotificationService.cs#L84-L93

The failure label is only added when an exception is thrown, not when the category is "Failed" due to recent build failures:

https://github.com/dotnet/docker-tools/blob/6b2d022bdc30337399970a962c2c933ee95d2c8c/src/ImageBuilder/Commands/QueueBuildCommand.cs#L191-L206

https://github.com/dotnet/docker-tools/blob/6b2d022bdc30337399970a962c2c933ee95d2c8c/src/ImageBuilder/Commands/QueueBuildCommand.cs#L269-L273

This means "AutoBuilder - Failed" issues are filed and immediately closed. These issues are actionable and should be left open so that they are visible and can be triaged.

Dominant language
C#
Stars
182
Forks
67
Avg merge
1d 20h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/docker-tools

All issues in dotnet/docker-tools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.