| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-04-09 | Tracking issue template: fine-grained information on style update status | Josh Triplett | -1/+4 | |
| Inspired by some of the communication issues around the stabilization of `let`-chains, give more fine-grained information about the status of updating style for any new syntax. This does not change the process or blockers in any way; it only *documents* the current state in the tracking issue. For instance, in the case of `let`-chains, we would have checked the boxes for "Style team decision" and "(non-blocking) Formatting has been implemented", and not checked the box for the style guide. That would have then provided better supporting information for any decisions. | ||||
| 2024-11-07 | chore(issue-template): fix branch name | ismailarilik | -1/+1 | |
| It was renamed to "main" from "master". | ||||
| 2024-04-24 | Strengthen tracking issue policy with consequences | Oli Scherer | -0/+2 | |
| 2023-07-11 | Mention style for new syntax in tracking issue template | Michael Goulet | -0/+3 | |
| 2021-01-22 | Note library tracking issue template in tracking issue template. | Mara Bos | -0/+2 | |
| 2020-09-05 | Fix typo in tracking issue template | dylni | -1/+1 | |
| 2020-04-18 | Clarify when to use the tracking issue template | Jonas Schievink | -1/+1 | |
| 2020-03-10 | rust-lang.github.io/rustc-dev-guide -> rustc-dev-guide.rust-lang.org | Santiago Pastorino | -2/+2 | |
| 2020-03-10 | Rename rustc-guide to rustc-dev-guide | Santiago Pastorino | -4/+4 | |
| 2020-01-21 | Add GitHub issue templates | Erin Power | -0/+58 | |
