Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

batches: don't count archived changesets towards completion percentage #46830

@courier-new

Description

@courier-new

Customers have reported confusion about how archived changesets factor into the batch change overall completion percentage. Presently, archived is treated as incomplete, but this doesn't make much sense given what archived actually means. If a changeset is archived, it means the repo no longer matched the on: statement in the batch spec. The PR is closed but kept associated with the batch change for the purposes of maintaining a historical record. With this meaning for context, it makes more sense to exclude archived changesets from the completion percentage calculation altogether, as we do with deleted changesets.

We should also consider clarifying how the completion percentage is computed with a tooltip from the UI.

Metadata

Metadata

Assignees

Labels

batch-changesIssues related to Batch Changes

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions