Skip to content

Use paths and paths-ignore to limit number of CI trigger conditions #197

@MMMalik

Description

@MMMalik

Are you reporting a feature request or a bug?

Task

Provide detailed reproduction steps (if any)

  1. Push commit / submit PR
  2. Observe that CI pipeline is triggered on changes to any file

Expected result

Tests should be triggered only for changes made to files that have impact on production build.

Actual result

CI jobs are triggered on changes to any file.

Possible solution

This behavior can be bypassed by adding keywords such as [skip-ci] to commit messages. As an alternative, investigate if paths and paths-ignore feature can be used to auto-detect relevant changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:confirmedAn issue confirmed by the development team.type:taskAny other issue (refactoring, typo fix, etc).

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions