You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2019. It is now read-only.
In IRC, @sole and @belen-albeza noted that Servo and Emscripten only track their bugs on GitHub, so we don't have a way to get them to show up in our dashboard.
How do we fix this?
Ideas:
Lobby BMO to add a "GitHub Tracking" component, where we can file duplicate tracking bugs that point to things on GitHub
Maintain a manual list (JSON document?) of bugs we want to watch. Maybe something like: {"organization/repo": { "p1": [ 32, 102, 74, 5 ], ... }, ... }?
Build a GitHub bot that we can @-mention whenever we want to track a bug, and use its notifications / webhooks to automatically maintain a list of bugs we're tracking.
What do y'all think? Any other ideas?
I'm fond of the manual list idea, just since it would be so easy to get started...
The text was updated successfully, but these errors were encountered:
The list might be the easiest probably as we don't need to duplicate effort filing 2 bugs
Do you think we could just give you the url instead of splitting in org/repo: number?
In IRC, @sole and @belen-albeza noted that Servo and Emscripten only track their bugs on GitHub, so we don't have a way to get them to show up in our dashboard.
How do we fix this?
Ideas:
{"organization/repo": { "p1": [ 32, 102, 74, 5 ], ... }, ... }
?What do y'all think? Any other ideas?
I'm fond of the manual list idea, just since it would be so easy to get started...
The text was updated successfully, but these errors were encountered: