-
Notifications
You must be signed in to change notification settings - Fork 97
Automatically create tracking issues when major change are accepted #2202
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
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-trackinglabel 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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Done, added the
${mcp_author}variable to get the handle of the MCP issue author.That would require some sort of easily-parseble format for triagebot, it's currently a free for all. Let's defer that for now.