Skip to content

Conversation

@Urgau
Copy link
Member

@Urgau Urgau commented Oct 17, 2025

This PR adds the required infrastructure to automatically create a tracking issues when a major change is accepted.

[major-change.tracking-issue-template]
repository = "triagebot"
title = "Tracking issue for MCP#${mcp_number}"
body = """
Multi line body with ${mcp_number} and ${mcp_title}
"""
labels = ["C-tracking-issue", "T-compiler"]

Fixes #2067
cc @fmease

@Urgau Urgau requested a review from Kobzol October 17, 2025 17:33
Copy link
Member

@Kobzol Kobzol left a comment

Choose a reason for hiding this comment

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

Implementation looks good!

View changes since this review

Copy link
Member

@fmease fmease Oct 17, 2025

Choose a reason for hiding this comment

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

This looks great, thanks!

I don't want to smother you with extra work, so these things can be done as follow-ups (or not all :P): In my issue & MCP I also proposed to

  • have some suppress-auto-tracking label to suppress the creation of the tracking issue.

    So it would be pretty great if one was able to register such a label in [major-change.tracking-issue-template] assuming you agree that such a mechanism would be useful (IIRC @Kobzol doubted the usefulness).

    That could come in clutch in situations like open MCP Remove diagnostic translation infrastructure compiler-team#924 where we already have a tracking issue: Tracking Issue for rustc's translatable diagnostics infrastructure rust#132181 (sort of). And IIRC my MCP / issue had some other vague examples?

  • have a way to ping the MCP author (and registered mentors if technically feasible) since the link to the MCP can be easily missed; however, it's probably not worth the effort

Copy link
Member Author

Choose a reason for hiding this comment

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

  • have some suppress-auto-tracking label to suppress the creation of the tracking issue

While I don't doubt the usefulness in some scenario I think they are going to be extremely limited. Even in your example I would still want to have the tracking issue created as they wouldn't track the same thing.

If we see the need for it we can always add it later.

  • have a way to ping the MCP author

Done, added the ${mcp_author} variable to get the handle of the MCP issue author.

  • and registered mentors if technically feasible

That would require some sort of easily-parseble format for triagebot, it's currently a free for all. Let's defer that for now.

@Urgau Urgau force-pushed the mcp-tracking-issue branch from 0185245 to 16c51bc Compare October 17, 2025 20:22
@Urgau Urgau added this pull request to the merge queue Oct 17, 2025
Merged via the queue into rust-lang:master with commit ef22f9b Oct 17, 2025
3 checks passed
@Urgau Urgau deleted the mcp-tracking-issue branch October 17, 2025 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature request: Auto-create a tracking issue for accepted MCPs

3 participants