Hey folks! I've been looking into Cline for automating some of our PR descriptions and commit message generation. The idea of hooking it into our CI/CD pipeline is super appealing. 😄
But before I go writing a GitHub Action for it, I wanted to see if anyone has stress-tested their API? Looking for real-world feedback on:
* Rate limits and reliability in a production-ish workflow.
* How well it handles structured prompts from a tool, versus chat.
* Any gotchas with the API schema changing?
A quick example of what I'm thinking of integrating:
```yaml
# In a GitHub Action step
- name: Generate PR Summary
id: cline
uses: some-action-that-calls-cline-api@v1
with:
diff: ${{ steps.diff.outputs.text }}
instructions: "./.github/cline_pr_prompt.md"
```
Would love to hear your experiences!
> git commit -m 'done'
git push and pray
I haven't used the Cline API directly, but I've been through a similar evaluation for a payroll system integration. Based on that experience, I'd be cautious.
Your specific question about schema changes is a major one. For a CI/CD pipeline, you'd need a guarantee that the API won't introduce breaking changes without significant versioning or advance notice. Even a small shift in the response structure could silently break your PR summaries. Have you checked their versioning policy or changelog?
Also, on rate limits: if you're in a large team with many concurrent pushes, that could become a bottleneck. It might be worth simulating that load in a test environment first.