@@ -440,15 +440,8 @@ Just a few things to keep in mind:
440
440
- The date the comment was added, e.g. instead of writing _ "Currently, ..."_
441
441
or _ "As of now, ..."_ , consider writing
442
442
_ "As of January 2021, ..."_ .
443
- Try to format the date as ` <MONTH> <YEAR> ` to ease search.
444
-
445
- - Additionally, include a machine-readable comment of the form `<!-- date:
446
- 2022-04 -->` (if the current month is April 2022). We have an automated
447
- tool that uses these (in ` ci/date-check ` ).
448
-
449
- So, for the month of April 2022, the comment would look like: `As of <!--
450
- date: 2022-04 --> April 2022` . Make sure to put the comment *between* ` as of`
451
- and ` April 2022 ` ; see [ PR #1066 ] [ rdg#1066 ] for the rationale.
443
+ We have CI action (in ` "~/.github/workflows/date-check.yml" ` )
444
+ that generates an issue if any of these are over 6 months old.
452
445
453
446
- A link to a relevant WG, tracking issue, ` rustc ` rustdoc page, or similar, that may provide
454
447
further explanation for the change process or a way to verify that the information is not
@@ -460,7 +453,6 @@ Just a few things to keep in mind:
460
453
461
454
[ rdg ] : https://rustc-dev-guide.rust-lang.org/
462
455
[ rdgrepo ] : https://github.com/rust-lang/rustc-dev-guide
463
- [ rdg#1066 ] : https://github.com/rust-lang/rustc-dev-guide/pull/1066
464
456
465
457
## Issue Triage
466
458
0 commit comments