Repository navigation
Conversation
siisee11
approved these changes
Sep 26, 2026
siisee11
left a comment
siisee11
left a comment
Contributor
There was a problem hiding this comment.
Reviewed after the main-branch conflict resolution. The Worker routes now expose /hooks/* and /open/* on both briar.onequery.dev and the legacy briar.wordbricks.ai domain. Wrangler dry-run completed successfully, and both paths are included in assets.run_worker_first.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
briar.onequery.dev/hooks/*and/open/*to thebriar-apiWorker routes so webhook endpoints and public issue share links on the current domain reach the Worker. Retain the correspondingbriar.wordbricks.airoutes for old-link compatibility if that hostname is restored. This branch was merged with currentmain(45275dd) and the wrangler.jsonc conflict was resolved.No production deployment was made. Before merging/deploying, the host should verify Cloudflare route configuration for the new zone and decide how to handle the old hostname, which currently has no DNS. After deploy, test a real webhook and signed-in/public share link on the new domain. Four required signoff checks remain expected and need to be run by the repo's normal process.