Skip to content
This repository has been archived by the owner on Jan 18, 2019. It is now read-only.

How should we track bugs in GitHub? #21

Open
callahad opened this issue Jun 9, 2016 · 2 comments
Open

How should we track bugs in GitHub? #21

callahad opened this issue Jun 9, 2016 · 2 comments

Comments

@callahad
Copy link
Contributor

callahad commented Jun 9, 2016

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...

@sole
Copy link
Contributor

sole commented Jun 9, 2016

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?

@callahad
Copy link
Contributor Author

callahad commented Jun 9, 2016

Sure. I thought just typing the number would be easier for human data entry, but if you prefer URLs, we can do URLs ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants