-
Notifications
You must be signed in to change notification settings - Fork 77
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
Zulip topic is only renamed for messages after MCP issue rename occurs #1228
Comments
@rustbot label: bug |
I was recently bit by this and ended up with 3 topics for my MCP. Thankfully the discussion didn't fork and stayed on the originally named topic. I think this can be fixed by just using the I also just noticed that I'm going to post a PR as this is just a simple one line fix (in theory...), however I don't have any kind of triagebot dev instance running to test this out myself. |
Oh, I've posted my PR, but now I think I may have misunderstood this bug. Is the issue not that the "Zulip topic is only renamed for messages after MCP issue rename occurs", but instead that doing so breaks the links in the MCP? |
Rename the entire zulip topic when an MCP issue is renamed. Fixes #1228.
I think |
It happened here. triagebot renamed the topic of the "renaming this Zulip topic" message, which effectively splits the topic in two, when it should have renamed the topic of the original "new proposal" message.
The code that is responsible for renaming the topic is here:
triagebot/src/handlers/major_change.rs
Lines 138 to 143 in 3272855
Another bug is that renaming the Zulip topic breaks the link in the MCP issue—which is what #711 was originally trying to fix (see #701, the short summary is that someone manually renamed the Zulip topic, which broke the link in the MCP issue).
Fixing these issues is probably going to be difficult. I'm not sure what the right solution is.
The text was updated successfully, but these errors were encountered: