Skip to content

[BUG] targetBranch needs remote #577

@mateusoliveira43

Description

@mateusoliveira43

Is this a BUG REPORT or FEATURE REQUEST?:

BUG

Version of Helm and Kubernetes:

ct version

Version:	 v3.9.0
Git commit:	 88cc7026481da7468e34a614b8ca4f0da42c063c
Date:		 2023-07-10T16:57:18Z
License:	 Apache 2.0

What happened:

With the add of verify if targetBranch is present in git repo, ct lint fails with false positive of failed linting charts: failed identifying charts to process: targetBranch 'master' does not exist.

What you expected to happen:

ct run normally.

How to reproduce it (as minimally and precisely as possible):

You need to run ct targeting a remote not default, since this command does not use remote information.

Ex.: ct lint --remote other --config ct.yaml --target-branch master --debug

Also, a CI run with this error.

Note: This is not fixed with passing target-branch as "remote/branch", as it fails the following check.

Another CI run with the other error.

Metadata

Metadata

Assignees

No one assigned

    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