Skip to content

Add column to summary to include skip reason #4055

@gep13

Description

@gep13

There are times when running a build, when one or more tasks are skipped. Currently, in order to know what caused the task to be skipped, you have to be running in diagnostic mode, and also you have to scroll up through the build output to see the skip reason.

I think it would be useful to include the skip reason for a task in the summary output that is reported at the end of a build.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions