Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pushPins / fetchPins fiasco #19

Open
terabyte opened this issue Mar 12, 2018 · 0 comments
Open

pushPins / fetchPins fiasco #19

terabyte opened this issue Mar 12, 2018 · 0 comments
Labels
discussion Potential change that requires discussion enhancement help wanted meta_tools impacts code in the meta-tools repo

Comments

@terabyte
Copy link
Member

pins remain one of the most annoying aspects of day-to-day QBT usage. @amling suggests possibly having a pushHooksDriver (similar to mergeDriver) that can figure out the remote name, show the qbt-manifest out of whatever you are pushing, and pushPins as well to the appropriate place.

Open to other ideas as well.
@terabyte terabyte added enhancement help wanted meta_tools impacts code in the meta-tools repo discussion Potential change that requires discussion labels Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion Potential change that requires discussion enhancement help wanted meta_tools impacts code in the meta-tools repo
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@terabyte