-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Tracking] Collect small but useful markdown edits & implement all at once #20304
Comments
Not enough to fix for now, postponing |
Not enough to fix still |
Can I get an opinion on adding this issue to the tracker? |
I like that plan 👍 seems super small but useful to get the fix in "eventually" 👍 |
Not enough to fix still |
👋 Alex, I'm curious what "enough" is? It seems like there's a bit of an inconsistency where some small markdown bugs are going through to be fixed irrespective of this issue to aggregate and tackle them as one. It kinda' makes this a bit redundant if a small fraction are just going to sit on hold while the majority go through and be fixed. |
That's fair, maybe we can just let them all go through and get fixed as normal 🤷 It's similar to the focus issues, it would be nice to try to batch them but nobody has prioritized figuring out a system for that |
Yeah, there's no point holding a few if everyone isn't following the same path to aggregate them to one issue to handle as a batch. |
yep def agreed 👍 do you want to start a slack convo about this? Or should we just close this one out? :D |
I think you can close this out and reopen the two issues that were closed. I'll take mine off hold :) |
ok we're moving forward with individual issues, killing this tracker |
Problem
There's a decent amount of super small, super edge case Markdown edits we may want to make eventually. This isn't a great ROI so most haven't been worked yet and are just closed as they come up
Solution
Use this issue to keep track of them as they come up, and eventually consider fixing them all at once if the ROI is high enough
Markdown issues being tracked
The text was updated successfully, but these errors were encountered: