GitHub user vasukiiyengar98 added a comment to the discussion: [GitHub] Workflow runs with in_progress status are skipped and not collected after completion
Thanks a lot for checking this and for the detailed explanation. In our setup, we have configured the GitHub Workflow Runs sync policy to run every 2 hours (0 */2 * * *), because we have production workflows that can run for around 3–4 hours. Our intention is to capture those workflow runs through the regular incremental sync once they complete. However, because the runs are skipped while they are in_progress, the later incremental sync doesn't pick them up after they become completed. You mentioned that a full/backfill sync or a timeAfter window covering the workflow runs' created_at can be used as a workaround. Could you please explain how we can configure this in our current DevLake version (v1.0.2)? We currently don't see an option in the UI to configure a recurring full/backfill sync or a timeAfter window for this purpose. If there is a specific configuration, API, or task setting we should use, could you please point us in the right direction? Also, if this behavior is something planned to be fixed in the GitHub plugin, it would be very helpful to know which future version we could expect the fix in. Thanks again for your help. DevLake is a great platform and it has already helped us solve several issues with our engineering data and reporting. We really appreciate the work from the team and community. GitHub link: https://github.com/apache/devlake/discussions/9125#discussioncomment-18366155 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
