chore: moved the docs links to individual config files#3861
Conversation
Signed-off-by: Efren Lim <elim@linuxfoundation.org>
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
In this PR
Ticket
CM-991
Note
Low Risk
Configuration-only change that alters where documentation URLs are sourced; main risk is incorrect/missing links for specific integrations.
Overview
Moves per-integration documentation URLs out of
links.tsand into each integration’sIntegrationConfigvia a new optionallinkfield.Updates the admin integration drawer “Learn more” link to read from
integration.linkwith a fallback to the globallinks.integrationsURL, and removes the now-unusedlinks.integrationLinksmap.Written by Cursor Bugbot for commit 7d3f908. This will update automatically on new commits. Configure here.