dco-check

dco-check copied to clipboard

GitLabRetriever does not work with pipelines for merge requests

6

When the [pipelines for merge requests](https://docs.gitlab.com/ee/ci/pipelines/merge_request_pipelines.html) feature is used, `dco-check` fails with the following error: ``` Options: check_merge_commits: False default_branch: master default_branch_from_remote: False default_remote: origin quiet: False verbose: True Detected:...

rmelotte

Fails when source branch has been merged in the target branch before

1

(The following applies to the GitRetriever). In case the source branch has already been merged into the target branch before, dco-check silently fails: ``` dco-check --verbose Options: check_merge_commits: False default_branch:...

rmelotte

dco-check run as GH action fails after extensive rebase

3

Kia ora, I added dco-check to GH, thank you for that, it's awesome :), and it flagged that a bunch of my commits weren't DCO compliant, so I rebased from...

LiamClarkeNZ

GitLab integration fails with detached pipelines for mere requests

6

Our project is using _pipelines for merge requests_. This feature is documented at https://docs.gitlab.com/ee/ci/merge_request_pipelines/ In the default recommended setup, dco-check 0.0.11 fails as follows: ``` dco-check Detected: GitLab could not...

zyga

See here: https://github.com/christophebedard/dco-check/pull/94#issuecomment-789200943 For example, in the comment linked above, I created a new project and pushed a first commit. This created the default branch (master) at the same time....

christophebedard

In situations where `dco-check` is used in a detected CI, a lot of the CLI options aren't used (e.g. default branch in GitLab).

christophebedard

Follow-up to #2 Currently, the supported CIs are tested by actually running `dco-check` (via a test) in PRs. That only tests a portion of the features: it doesn't test pushing...

christophebedard