Skip to content

fix(notifications): Stop generating legacy Rule links - #128081

Open
kcons wants to merge 2 commits into
masterfrom
kcons/leglink
Open

kcons wants to merge 2 commits into
masterfrom
kcons/leglink

Conversation

@kcons

@kcons kcons commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

This is valuable, because we need to stop generating '/rules/' links if we want to get rid of the redirects for them.

Issue-alert notification links now resolve only from workflow identities. Origins without a workflow no longer generate legacy Rule links, and digest templates key link metadata by workflow_id instead of the compatibility link_id.

This keeps rendered notification links on the workflow UI and establishes workflow IDs as the rendering identity before the notification analytics fields are migrated separately.

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 19, 2026
@kcons

kcons commented Oct 31, 2026

Copy link
Copy Markdown
Member Author

bugbot review

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit cba3e65. Configure here.

@kcons
kcons marked this pull request as ready for review October 31, 2026 00:15
@kcons
kcons requested review from a team as code owners October 31, 2026 00:15

This branch was successfully deployed

1 active (outdated) deployment
Preview — 3b958c56 Deployed Oct 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant