-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: ability to filter on status context existence #189
base: master
Are you sure you want to change the base?
Conversation
We've been using this code for about a month now and it's been working great. Would love some feedback when anyone has time to permit. Thanks! |
@itsdalmo Do you think we can get this merged? I would like to prevent us from needing to fork the resource to be able to get passed this issue. |
I can probably get it cleaned up sometime later this week or next week. |
bad7c2b
to
e3fc941
Compare
@rickardl I rebased from master and fixed conflicts. I'll work to update our internal fork and verify it continues to work as expected. |
Hello, is there a chance we could have a new release with this fixed? |
Someone fix the conflict, please!! |
Working to update with latest code from master now that #233 is hopefully addressed |
@jmccann Excellent, thank you so much for your help. |
Looks like my updates conflict with latest code ... I tried to add them but stuff broke ... need to spend more time on this 😢 |
Hi @jmccann, which test is failing for you? I rebased onto master with one conflict, and everything is working for me. |
@jhosteny The issue I am having is it's not working as expected when I use it in my test environment. The Are you using it and it seems to be working as expected? 🤔 |
Think I found the issue ... I didn't rebase and tried to patch in manually and undid some other recent changes ... think I'll have this updated soon |
e3fc941
to
67d75f9
Compare
It's looking good so far. 👍 |
Been using this for several days now and haven't seen any issues. So it's up to a reviewer now on this getting merged. 😄 |
If it helps, we've also been using this in a private build of the resource for months without issue (along with the submodule fix, #200). We definitely have some repositories whose workflow tends to exercise the issue, and this change fixed it. |
Hello, any news if this can be merged? I love the resource - it is very useful but we did get hit by that bug multiple times. |
Evening? Is there a chance this PR gets merged? Every week once or twice our team gets hit by the problem of PR's not being picked up. |
@rickardl any chance this can get integrated into master? |
Asking for any update if this can be merged.? |
Taking a stab at fixing #26, which basically is resulting in commits being missed on
check
in certain conditions.The core problem seems to stem from the fact that we are using the commit date to filter out "old" versions. But under certain conditions we may miss some commits on an initial check. Subsequent check will continue to miss the commit as we are now filtering it out based on the date/time of the "latest version".
So instead of using a datetime filter I've added a feature to allow filtering "old commits" based on if they have a status check associated with the SHA. The status check to look for is configured by a new
status_check
param to the source configuration.I've been quickly testing this locally and it seems to be working! PR/commit that missed the provided status check are reported on. PR/commit that already have the status check are filtered out.
I left in the commit datetime filtering logic. But if
status_check
is provided the feature is disabled in favor of using status checks to filter out old commits.Looking forwards to comments/questions/suggestions!
fixes #26