Implementing Issues

[dlvhdr]

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

• The name of the repo is problematic. Is it possible to easily rename an existing github repo?
• Create a different repo - that will basically be a 90% copy paste of this one (this bothers me a bit :D)

UI

• If we go with a single tool for both PRs and issues we need to think how it will look

[dlvhdr]

@abdfnx @micalevisk

[abdfnx]

Hi bro @dlvhdr

[abdfnx]

ok @dlvhdr , I well think about an awesome name, if I found, I'm going to tell you

[abdfnx]

and of course we need to add issues to this powerful app

[micalevisk]

I would love to see an extension for both PRs and Issues! filters must allow is:issue and is:pr

Is it possible to easily rename an existing github repo?

yep. But I guess the extension gh-prs won't exist anymore.

Create a different repo

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.

[dlvhdr]

Oh cool, I'll take a look.
I guess I don't really care if the extension won't exist. We'll just update the README installation instructions and people upgrading a version will need to install the new extension.

Let's say the new extension is called gh-dashboard.
I was thinking of 2 ways to implement this:

1. In order to see PRs you will run gh dashboard prs and issues gh dashboard issues.
2. A single gh dashboard command will allow switching between prs and issues through the UI.

[micalevisk]

yeah, I prefer splitting them too. gh dashboard looks good to me but I'll create an alias to make it shorter
gh alias set prs 'dashboard prs'
gh alias set iz 'dashboard issues'

😄

[dlvhdr]

What does iz means?

[micalevisk]

"ss" = "z" because I don't want to type issues xD

[abdfnx]

and for

1. In order to see PRs you will run gh dashboard prs and issues gh dashboard issues.

I think replacing it with gh dashboard -p/--prs and for issues gh dashboard -i/--iz will be better

[micalevisk]

oh, another approach to help people migrating to the new extension would be:

1. create a fork of the repo and rename it to gh-prs
2. publish a minor of gh-prs that does nothing but just display a message like: This extension was replaced by dlvhdr/gh-dashboard. You can use gh alias set prs 'dashboard prs'

[abdfnx]

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 Ctrl+S or s key handlers for this panel or dialog or what ever do you want to name it

[abdfnx]

what do you think @dlvhdr @micalevisk ?

[dlvhdr]

Cool idea @abdfnx :) I like it!

[micalevisk]

me too.

[abdfnx]

what about gh-dash name, it's shorter and easy to remember

[micalevisk]

yeah, to me that's better. But as gh have the alias feature, the name itself doesn't really matter that much I guess. As long it is good enough to find easily on github.

[abdfnx]

@dlvhdr You outdid yourself, a few months ago your gh-prs repo was simple and now it's great
thank you for this helpful extension

[zackproser]

Agree. This is really beautiful work.

[dlvhdr]

@abdfnx @zackproser @micalevisk check out the latest release :)

[abdfnx]

nice work bro

[abdfnx]

I like it

[zackproser]

@dlvhdr Awesome 🎉 - thank you very much! Looks great - shared it internally at work, too.