-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
[Roadmap] Make issue numbers clickable #284
Comments
Or some kind of reference that is searchable here? |
I started searching for how to add links to the issue numbers on roadmap page. After some digging, I found out that Mastodon is using https://linear.app/ to track the progress of their roadmap. They are using Linear's API to retrieve the data and then using it into the Roadmap page. Check out the Line 14 in 2daebb3
It basically makes an API call to Linear using their own LINEAR_API_KEY, Line 7 in 2daebb3
Retreives the data and stores it in linear.json file. I think the links won't be available publicly anyway. Let me know what you think. |
I agree. The final, internal issue tracker is private. And actually I don't have a problem with that. They do need a place for a conversation without all of us contributing. And we don't need full visibility of internal discussion. But I would like to see a bit more information being available to the public, rather than just, this is maybe a candidate, maybe. Perhaps they could have a field in each linear-issue that says: this is what's happening, the topic is known to be under discuss ion in this/these github-issue/s... And then we can click on the issue to expand it and see the current content of that field. I mean, I guess, any of us could start creating a github-issue for each linear-issue. But it would be better to have something endorsed by the dev team. Just keep us "consulted/informed", please. |
The issue numbers (i.e.
MAS-23
) should be clickable and point to the actual issues and PRs, if that is doable.The text was updated successfully, but these errors were encountered: