Skip to content

fixing some improperly escaped URLs #19739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 11, 2025
Merged

fixing some improperly escaped URLs #19739

merged 2 commits into from
Jun 11, 2025

Conversation

jonjanego
Copy link
Member

No description provided.

@Copilot Copilot AI review requested due to automatic review settings June 11, 2025 21:08
@jonjanego jonjanego requested a review from a team as a code owner June 11, 2025 21:08
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Fix improperly escaped URLs by removing angle brackets around the GitHub pull request link in release notes and the main changelog.

  • Removed < and > around the PR URL to conform with markdown’s auto-linking.
  • Applied the same formatting change in both the 1.3.0 change notes and the top-level CHANGELOG.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
go/ql/src/change-notes/released/1.3.0.md Removed angle brackets around the PR URL link.
go/ql/src/CHANGELOG.md Removed angle brackets around the PR URL link.

@jonjanego jonjanego merged commit 6ec4811 into main Jun 11, 2025
11 checks passed
@jonjanego jonjanego deleted the changedocs-2.22.0 branch June 11, 2025 21:24
@owen-mc
Copy link
Contributor

owen-mc commented Jun 12, 2025

I wrote that original changelog. Should I have used this formatting at that point? I wasn't aware of that markdown syntax, but now I look for it I see it.

@jonjanego
Copy link
Member Author

I wrote that original changelog. Should I have used this formatting at that point? I wasn't aware of that markdown syntax, but now I look for it I see it.

I think at this point has @turbo updated our doc builder script to handle Markdown autolink so it's not a problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants