Klesh Wong

LGTM, did you test it? did it work?

I am afraid this would affect helm chart and release procedure as well. We need more input about this @matrixji @JorgeGar @d4x1 What do you guys think?

Can't reproduce.   According to the code https://github.com/apache/incubator-devlake/blob/b34d5258dee9d6703df6d2915703323fdaa6c1b5/backend/plugins/github/api/blueprint_v200.go#L126 It would always pick the first token for collecting git data. The error message you posted contains "remote: Support for password...

Were any of them fine-grained tokens?

Can you share screenshots of the connection detail page for those scopes that are NOT inheriting scope config?

@gustavobini I recently finished a PoC of Increment Mode support for JIRA issue changelog extractor and converter. It might be helpful to your aim. https://github.com/apache/incubator-devlake/pull/7394

The problem stems from the `issue_collector` and its Incremental Collection feature. Currently, this feature relies on the `updated_at` timestamp of issues, which unfortunately isn't updated when only labels are changed....

@michelengelen You may check the code: If a subtask uses a stateful helper, it supports Incremental Mode and it would work that way unless you force the Full Sync model:...

@michelengelen Nice work. If the `issue.updated_at` is in fact updated, it should be collected in Incremental Mode. I am not familiar with the `graphql` , can you help check if...

Yes, it does, thanks for the information. Will look into it later.