search

Kir-Antipov / GitHub-Defreshed

:octocat: Classical GitHub at its finest
MIT License
83 stars 3 forks source link

What should we do next? #21

Open Kir-Antipov opened 4 years ago

Kir-Antipov commented 4 years ago

The script fulfilled its main purpose and gave us back the old GitHub layout, but should we stop there? Or should we go further and implement some features that GitHub has always lacked?

Since we can customize the behavior of the script, there will be no conflict of interest for those who want to leave everything as it is and those who want to add something, so it seems to me that we can go ahead and expand the capabilities of GitHub.

What do you think about it? It would be great to hear your thoughts and suggestions!

An-dz commented 4 years ago

I always wanted to see the version number in the summary bar and that's something that was added somewhat hidden in the new crappy layout.

I think adding a popup that when hovering the releases button shows the latest version number/name and when it was released and then an option to change which shows in the popup and which in the text would be nice. This way both options can see the latest version number and the number of releases.

And perhaps an option to have the languages information always open by default.

Kir-Antipov commented 4 years ago

I always wanted to see the version number in the summary bar and that's something that was added somewhat hidden in the new crappy layout.

I think adding a popup that when hovering the releases button shows the latest version number/name and when it was released and then an option to change which shows in the popup and which in the text would be nice. This way both options can see the latest version number and the number of releases.

Absolutely love this idea!

And perhaps an option to have the languages information always open by default

I think, it makes sense. Anyway, it's really easy to implement :)