In the initial implementation, we agreed that the webhook backend endpoint would process one commit with one file per webhook request.
However, in some scenarios, we push multiple commits per request, typically when merging a pull request with a new batch of AI transcripts. While our initial agreement focused on one commit per request, we need to support cases where multiple commits are present within a single request.
The current implementation works when we have multiple commits within a single request, but with limitations. When an issue occurs with the processing of one transcript/commit in a multi-commit request, it impacts the processing of subsequent files.
kouloumos
commented
8 months ago
In the initial implementation, we agreed that the webhook backend endpoint would process one commit with one file per webhook request.
However, in some scenarios, we push multiple commits per request, typically when merging a pull request with a new batch of AI transcripts. While our initial agreement focused on one commit per request, we need to support cases where multiple commits are present within a single request.
The current implementation works when we have multiple commits within a single request, but with limitations. When an issue occurs with the processing of one transcript/commit in a multi-commit request, it impacts the processing of subsequent files.