Skip to content

Inconsistent behavior of isClean check #21

@lwolf

Description

@lwolf

For some reason !isClean() introduced in the #3 doesn't always work as expected.

Here is the output from git status and cob:

$ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

$ cob
2020/07/02 15:30:59 the repository is dirty: commit all changes before running 'cob'

This fails both locally and in the CI for some repos, but doesn't fail for others.

Could this check be optional, so it could be force disabled in the CI where one doesn't care about loosing state.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions