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
It'd be nice if there were a way to define groups of repos that could be re-used.
Use Case
I work on a framework that is used in lots of projects both private and public. Because I work on things like new project setup, build, IDE support, etc, and there are things that cannot be fixed in a single project. This tool is great for that, but if I have 24 projects to clone an issue to, it defeats the purpose of this tool. (even just having < 5 that I would repeatedly clone to)
MVP - A single group persisted locally.
Better? - A single group persisted with chrome profile to use across desktops.
Wishful Thinking? - Easy management of groups.
My dream one day, be able to easily manage creation, duplication, etc, management of groups:
I would be happy with the tool having permissions to use a config file from a dedicated private repo since this would provide a lot of functionality desired just by using text editors and IDEs which have access to lots of tools like macros, etc.
Handy options only available if valid config source has been configured:
auto-fetch - brute just-in-time fetching
(there might be ways to make this more performant based on request headers, caching configuration in things like local storage, etc, but probably unnecessary pre-optimizations)
manual-fetch - provide an inline-ish way to click a little fetch icon where groups end up being displayed for selection.
The goal here is that it's easy to manually fetch without having to dive into options to do it, though providing manual fetch invocation in options would be the obvious scoped down way to satisfy the functionality.
The text was updated successfully, but these errors were encountered:
It'd be nice if there were a way to define groups of repos that could be re-used.
Use Case
I work on a framework that is used in lots of projects both private and public. Because I work on things like new project setup, build, IDE support, etc, and there are things that cannot be fixed in a single project. This tool is great for that, but if I have 24 projects to clone an issue to, it defeats the purpose of this tool. (even just having < 5 that I would repeatedly clone to)
MVP - A single group persisted locally.
Better? - A single group persisted with chrome profile to use across desktops.
Wishful Thinking? - Easy management of groups.
My dream one day, be able to easily manage creation, duplication, etc, management of groups:
I would be happy with the tool having permissions to use a config file from a dedicated private repo since this would provide a lot of functionality desired just by using text editors and IDEs which have access to lots of tools like macros, etc.
Handy options only available if valid config source has been configured:
(there might be ways to make this more performant based on request headers, caching configuration in things like local storage, etc, but probably unnecessary pre-optimizations)
The goal here is that it's easy to manually fetch without having to dive into options to do it, though providing manual fetch invocation in options would be the obvious scoped down way to satisfy the functionality.
The text was updated successfully, but these errors were encountered: