feat(workflow-engine): Hook into organization creation signals - #121471
Conversation
d4a6c58 to
9932a77
Compare
saponifi3d
left a comment
There was a problem hiding this comment.
Yayyyy!!!! Looks great!
9932a77 to
8c94d78
Compare
d63d24f to
7384516
Compare
This comment was marked as outdated.
This comment was marked as outdated.
|
dont |
0f1b9a6 to
1e061b5
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1e061b5. Configure here.
| workflows: list[Workflow], | ||
| ) -> Sequence[DetectorWorkflow]: | ||
| connections = [DetectorWorkflow(workflow=workflow, detector=detector) for workflow in workflows] | ||
| return DetectorWorkflow.objects.bulk_create(connections, ignore_conflicts=True) |
There was a problem hiding this comment.
Unused detector workflow helper
Low Severity
connect_workflows_to_detector is added but never called. Connection is already done inside create_and_connect_pull_request_workflow via DetectorWorkflow.objects.create, so this helper is dead code that mirrors the unused parallel to connect_workflows_to_issue_stream.
Reviewed by Cursor Bugbot for commit 1e061b5. Configure here.


Adds a new BetterSignal, and triggers it from the cell provisioning rpc for creating organizations. There is precedent for this with the
terms_acceptedsignal, so it should be okay.We're also adding the receiver, but it's gated by an option to be a noop on merge, we can control its rollout when we're ready.
Stack created with GitHub Stacks CLI • Give Feedback 💬