Replies: 9 comments 14 replies
-
ok @dlvhdr , I well think about an awesome name, if I found, I'm going to tell you |
Beta Was this translation helpful? Give feedback.
-
and of course we need to add issues to this powerful app |
Beta Was this translation helpful? Give feedback.
-
I would love to see an extension for both PRs and Issues!
yep. But I guess the extension
I've prototype this here in my fork: https://github.com/micalevisk/gh-prs it worked well so far but as I don't know Go, it's just a POC. |
Beta Was this translation helpful? Give feedback.
-
oh, another approach to help people migrating to the new extension would be:
|
Beta Was this translation helpful? Give feedback.
-
maybe I've good idea, when the user want to switch between pull requests and issues, you can create a panel like this and you can create |
Beta Was this translation helpful? Give feedback.
-
what about |
Beta Was this translation helpful? Give feedback.
-
@dlvhdr You outdid yourself, a few months ago your |
Beta Was this translation helpful? Give feedback.
-
@abdfnx @zackproser @micalevisk check out the latest release :) |
Beta Was this translation helpful? Give feedback.
-
Issues
I've seen some demand for supporting displaying issues.
I'm not sure what's the actual demand and how to really incorporate it.
Background
I've mainly developed this gh extension for myself and my use case was pretty simple:
Our team at @wix is using micro-frontends and this means A LOT of repos.
I wanted to know who's working on what, and a way to track my PRs across the repos.
Also, I thought it could be cool to see what other OSS repos I was interested in are working on.
I'm not really an OSS contributor so I didn't think issues were that important.
But I can see why it'd be important when you're maintaining a big OSS project.
Possible Solutions
UI
Beta Was this translation helpful? Give feedback.
All reactions