Lynwee

1. >Is DevLake correctly capturing the status of the pipeline? In our case "Warning" Pipeline's status is from `_raw_gitlab_api_pipeline_details.data`, there is a `status` field in it, you can check it....

1. It seems GitLab regard it as `success`, we cannot fetch the `warning` status and can do nothing with it. 2. fields' values in cicd_tasks are within my expectation. In...

> Hi @d4x1 , > > I think the missing part is to validate when the Environment is "Production" the Result should be "Success" in the cicd_tasks table for that...

@alexander-bloss How about this issue?

@lokeshmandhare We've tested the latest codes in main branch. Table `pull_request_reviewers` have expected records. You can try latest version: https://github.com/apache/incubator-devlake/releases/tag/v1.0.1-beta6. And in 44f3dea, it's normal that table `pull_request_reviewers` is empty....

@lokeshmandhare `pull_request_assignees` is empty means even there is a table `pull_request_assignees` in DevLake, but there is no code that write pull_requests' assginees to this table in plugin github, so it's...

@tomerc-everc How about this issue ?

> Yes @klesh these workflows ran in April current year. I even tried from the GitHub API and it brings me all the workflows without any problem. @daviddsp Can you...

@daviddsp Have you tried latest version(v1.0.x)?

@daviddsp Thanks for your feedback. We have two guesses: 1. Some workflow runs are not `completed` in your repo, because codes https://github.com/apache/incubator-devlake/blob/main/backend/plugins/github/tasks/cicd_run_collector.go#L97 which were added since v0.20 filter workflow runs,...