Before submitting
Area
apps/web
Problem or use case
I want to implement a full loop where once a PR is opened I have T3 code automatically create a new thread and start reviewing the comments of the PR from code review bots.
Proposed solution
Implement a button next to each project to open up project scoped automations with triggers inspired heavily by how Cursor automations work:
- Cron schedule
- Github triggers (PR opened, PR merged, new commit etc)
- Gitlab triggers
- Sentry triggers (new error found)
- Linear triggers (new issue etc)
It could also support template triggers and automation/triggers that can be reused, and automations/triggers that automatically get added to every project we work on.
Why this matters
This would make working with loops much more powerful and easier to configure within T3 code.
Smallest useful scope
Just the basic triggers with GitHub, like when a pull request is opened and a cron scheduled automations.
Alternatives considered
There isn't currently a workaround in T3 code at the moment, as far as I'm aware, but I know Theo mentioned on his latest video that he's interested in getting this implemented in some form at some point.
Risks or tradeoffs
No response
Examples or references
https://cursor.com/automate?cc_platform=google&cc_campaignid=23656700841&cc_adgroupid=197698806951&cc_adid=810459370493&cc_keyword=cursor%20automations&cc_matchtype=b&cc_device=c&cc_network=g&cc_placement=&cc_location=9192516&cc_adposition=&gad_campaignid=23656700841&gbraid=0AAAABAkdGgRwBZ8RnD1dxG8MLIv_jB6sW
Contribution
Before submitting
Area
apps/web
Problem or use case
I want to implement a full loop where once a PR is opened I have T3 code automatically create a new thread and start reviewing the comments of the PR from code review bots.
Proposed solution
Implement a button next to each project to open up project scoped automations with triggers inspired heavily by how Cursor automations work:
It could also support template triggers and automation/triggers that can be reused, and automations/triggers that automatically get added to every project we work on.
Why this matters
This would make working with loops much more powerful and easier to configure within T3 code.
Smallest useful scope
Just the basic triggers with GitHub, like when a pull request is opened and a cron scheduled automations.
Alternatives considered
There isn't currently a workaround in T3 code at the moment, as far as I'm aware, but I know Theo mentioned on his latest video that he's interested in getting this implemented in some form at some point.
Risks or tradeoffs
No response
Examples or references
https://cursor.com/automate?cc_platform=google&cc_campaignid=23656700841&cc_adgroupid=197698806951&cc_adid=810459370493&cc_keyword=cursor%20automations&cc_matchtype=b&cc_device=c&cc_network=g&cc_placement=&cc_location=9192516&cc_adposition=&gad_campaignid=23656700841&gbraid=0AAAABAkdGgRwBZ8RnD1dxG8MLIv_jB6sW
Contribution