Skip to content

Only trigger Github Actions python CI build when it is absolutely necessary #406

@chuck-sys

Description

@chuck-sys

Please give a one-sentence summary of the feature you would like to see.

When we make a pull request touching non-python files, we should not be required to burden Github (haha) with testing everything.

Please give as many details as possible about the requirements for the feature.

Instead, we can use Github Actions CI on.pull_request.paths to:

  1. Run tests specific for the appropriate changes (file extension globbing and whatnot)
  2. Have multiple tests run in parallel if, say, both documentation and code is modified, which makes it go faster slightly

You may have to do some experimenting on your own for this.

Please list any additional context.

@cheukyin699 was getting bored of waiting like 10 minutes for a build check to go through for the tiniest changes.

Metadata

Metadata

Assignees

Labels

theme:featureRequest a new feature.theme:toolingAdd or change our tooling, builds, or deployment

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