Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

use page titles as link text to avoid warnings#1532

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
nedbat merged 2 commits intopython:mainfromnedbat:nedbat/no-more-here
Mar 19, 2025

Conversation

nedbat
Copy link
Member

@nedbatnedbat commentedMar 18, 2025
edited by github-actionsbot
Loading

Previously we had scary red messages:

devguide/core-developers/memorialization.rst:5: WARNING: Duplicate explicit target name: "here". [docutils]devguide/core-developers/memorialization.rst:5: WARNING: Duplicate explicit target name: "here". [docutils]

📚 Documentation preview 📚:https://cpython-devguide--1532.org.readthedocs.build/

Previously we had scary red messages:```devguide/core-developers/memorialization.rst:5: WARNING: Duplicate explicit target name: "here". [docutils]devguide/core-developers/memorialization.rst:5: WARNING: Duplicate explicit target name: "here". [docutils]```
@nedbatnedbat requested a review fromambvMarch 18, 2025 12:23
@nedbat
Copy link
MemberAuthor

Though TBH, that warning seems kind of dumb to me... Maybe we can disable it? /cc@hugovk

@hugovk
Copy link
Member

A double trailing underscore make the link an "anonymous" one and avoids warnings:

-`here <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_.+`here <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`__.

@nedbat
Copy link
MemberAuthor

sigh there's always some other twist to learn about .rst.... I've used double-underscore in its other form:

Look over `there`__.__https://overthere.com

Copy link
Member

@ezio-melottiezio-melotti left a comment

Choose a reason for hiding this comment

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

In general the text of the link shouldn't be a generic text like "here" or "link", but should reflect the content of the page it links to, so rephrasing those links would be preferred.

If possible, the link should be the actual title of the page and/or the name of the service (e.g. "See also theDiscourse best practices for deceased community members"). Doing this will also avoid warnings.

Copy link
Member

@hugovkhugovk left a comment

Choose a reason for hiding this comment

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

ezio-melotti reacted with hooray emoji
The general policy regarding deceased users on GitHub is described
`here <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_.
The general policy regarding deceased users on GitHub is described on their
`GitHub Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
`GitHubDeceased User Policy<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
`Deceased User Policy<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_

Comment on lines 44 to 45
The general policy regarding deceased users on GitHub is described on their
`GitHub Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
Copy link
Member

Choose a reason for hiding this comment

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

Based on what we discussed, it would be better to include "GitHub" in the link, but the current sentence repeats it twice. I would either remove the other one:

Suggested change
The general policy regarding deceased userson GitHubis described on their
`GitHub Deceased User Policy<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
The general policy regarding deceased users is described on their
`GitHub Deceased User Policy<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_ page.

or simply:

Suggested change
The general policy regarding deceased users onGitHubis described on their
`GitHub Deceased User Policy<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
See also the `GitHubDeceased User Policy
<https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_ page.

@nedbat
Copy link
MemberAuthor

I've tweaked the GitHub link title to remove the duplication.

@nedbatnedbat merged commitf4df9cc intopython:mainMar 19, 2025
4 checks passed
@nedbatnedbat deleted the nedbat/no-more-here branchMarch 19, 2025 12:44
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@ezio-melottiezio-melottiezio-melotti left review comments

@hugovkhugovkhugovk approved these changes

@ambvambvAwaiting requested review from ambv

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@nedbat@hugovk@ezio-melotti

[8]ページ先頭

©2009-2025 Movatter.jp