Skip to content

ci: Add checks for targets to avoid future regressions #213

@eureka-cpu

Description

@eureka-cpu

We pretty much rely on people to open issues when things stop working, but there are some common cases we can at least account for, eg. linking issues and such. Just using the default and minimal to build the most problematic dependencies should do the trick and keep things from regressing.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions