Giter Site home page Giter Site logo

Comments (7)

christophebedard avatar christophebedard commented on June 9, 2024 1

This doesn't exist, but it could be added.

Ignoring commits starting from a given date is tricky, because commits are not necessarily ordered chronologically. It might work fine on a case-by-case basis depending on how the filtering is done (e.g., check commits starting from HEAD and stop checking them once the commit's date is before the given date).

What about providing a commit hash from which to start checking? Meaning only check from commit to HEAD.

from dco-check.

chschroeder avatar chschroeder commented on June 9, 2024

Thanks for the quick reply!

I followed your advice and found out about CI_COMMIT_BEFORE_SHA, which I set to the desired starting commit. This solves the problem (at least for my use case) :).

from dco-check.

christophebedard avatar christophebedard commented on June 9, 2024

Oh yeah, that works for GitLab CI specifically!

from dco-check.

chschroeder avatar chschroeder commented on June 9, 2024

The suggestion to provide a commit hash, this was just a thought for an enhancement and would not work yet with a Github CI, right? (My CI Pipeline might migrate towards Github in the future.)

from dco-check.

christophebedard avatar christophebedard commented on June 9, 2024

I had to re-read the documentation and code 😅

For pushes to the default branch, dco-check tries to only check new commits if possible. GitLab CI provides the hash of the last commit on the branch before the push, and GitHub does too:

commit_hash_base = self.event_payload['before']

So dco-check won't re-check old commits every time you merge a MR/PR. And assuming that the un-signed-off commits are already on the default branch, dco-check just won't re-check them.

The suggestion to provide a commit hash, this was just a thought for an enhancement

If there are corner cases or CI platforms that don't support the current behaviour you get with GitLab CI and GitHub CI, then yes an option could be added to never check commits before the given commit hash (inclusive). But as I said, I don't think you'll need this.

from dco-check.

chschroeder avatar chschroeder commented on June 9, 2024

Thanks a lot for the advice. Indeed, this sounds like this will not be a problem on Github and GitLab :).

from dco-check.

christophebedard avatar christophebedard commented on June 9, 2024

Let me know if you do have any issues!

from dco-check.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.