Skip to content

Commit 0fd0512

Browse files
Hugo and Petr's reviews
1 parent 6130cc3 commit 0fd0512

1 file changed

Lines changed: 5 additions & 9 deletions

File tree

triage/issue-tracker.rst

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ The `issue tracker`_ is hosted on GitHub, alongside the codebase and pull reques
1515
(sometimes called :dfn:`bpo` or :dfn:`BPO` for short). A read-only version is
1616
available on that domain for historical purposes. All ``bpo`` data has been
1717
migrated to the current issue tracker on GitHub.
18+
Old issues are still referenced in the :samp:`bpo-{NNN}` format,
19+
where ``bpo-12345`` refers to ``https://bugs.python.org/issue12345``.
1820

1921

2022
Reporting an issue
@@ -150,15 +152,9 @@ The following abbreviations can be used in a comment to generate a link:
150152

151153
See also the `list of autolinks supported by GitHub <autolinks_>`_.
152154

153-
To link to a file in the repository, use a Markdown link with the path
154-
of the file relative to the repository root, for example
155-
``[the os module docs](Doc/library/os.rst)``. In issues, such links
156-
point to the latest version of the file on the default branch. In PRs,
157-
they are resolved against the PR's branch instead, so prefer permanent
158-
links there.
159-
160-
You can get a permanent link to a given revision of a given file by
161-
`pressing "y" <https://docs.github.com/en/repositories/working-with-files/using-files/getting-permanent-links-to-files>`__.
155+
To link to a file in the repository, you can get a permanent link to a
156+
given revision of the file by `pressing "y"
157+
<https://docs.github.com/en/repositories/working-with-files/using-files/getting-permanent-links-to-files>`__.
162158

163159

164160
Following issues

0 commit comments

Comments
 (0)