Skip to content

Conversation

josevarghese
Copy link
Contributor

@josevarghese josevarghese commented Aug 8, 2025

Motivation for the change, related issues

Right now, the license hyperlink within the intro page for the languages es, pt-BR and ja are added with https://github.com/WordPress/blob/trunk/LICENSE, which is a 404 error page.

Implementation details

Changed the hyperlinks to the correct license page https://github.com/WordPress/wordpress-playground/blob/trunk/LICENSE

Testing Instructions (or ideally a Blueprint)

Visually inspect the updated license links.

broken link fix for ja language
Fixing the license broken link
broken link fix for the pt-BR language intro page
…he public one

Some changelogs this year are linked to Automattic's private repository, which is not accessible to the public who are not in Automattic, so I have replaced them with the public repo link.
@josevarghese josevarghese requested a review from a team as a code owner August 8, 2025 19:21
@josevarghese josevarghese changed the title Fixed all the PR links in the changelog from the Automattic repo to the public one Fixed all the PR links in the changelog from the Automattic repo to the public one and wrong license page within the languages es, pt-BR and ja Aug 8, 2025
@ajitbohra
Copy link
Member

PR links are not valid on this repo!

fork and this repo PR number are not in sync!

@WordPress/playground-maintainers thoughts on this? Should we drop PR links on changelog items pointing to the fork?

@zaerl
Copy link
Collaborator

zaerl commented Aug 14, 2025

PR links are not valid on this repo!
fork and this repo PR number are not in sync!
@WordPress/playground-maintainers thoughts on this? Should we drop PR links on changelog items pointing to the fork?

I think it's okay to have the fork URLs in some entries of the CHANGELOG.md file, as that's where the PRs were shipped at the time. Not in this repository.

…epo to the public one"

This reverts commit 44e2161.

The reason is that there are no valid public links for those private
PRs. We could consider omitting those links (which I believe we did
in the private repo at one time), but let's leave as-is for now.
@brandonpayton
Copy link
Member

PR links are not valid on this repo!
fork and this repo PR number are not in sync!
@WordPress/playground-maintainers thoughts on this? Should we drop PR links on changelog items pointing to the fork?

I think it's okay to have the fork URLs in some entries of the CHANGELOG.md file, as that's where the PRs were shipped at the time. Not in this repository.

@ajitbohra @zaerl This sounds reasonable to me. It's just the truth that that work was done in a separate, private repo.

@josevarghese, after this discussion, I went ahead and reverted the commit to update the CHANGELOG links and will review the rest of this PR after that.

@brandonpayton brandonpayton changed the title Fixed all the PR links in the changelog from the Automattic repo to the public one and wrong license page within the languages es, pt-BR and ja Fix wrong license page within the languages es, pt-BR and ja Aug 20, 2025
Copy link
Member

@brandonpayton brandonpayton left a comment

Choose a reason for hiding this comment

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

The updated license links look good to me. Thank you for the fixes!

@brandonpayton brandonpayton merged commit 7c83c64 into WordPress:trunk Aug 20, 2025
22 checks passed
@fellyph fellyph added the [Type] Documentation Improvements or additions to documentation label Aug 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants