-
-
Notifications
You must be signed in to change notification settings - Fork 266
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.
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
Feature request: Import from JSON? #1065
Comments
Maybe I'm missing something but I use Except for sharing between machines, I can envision other reasons for what amounts to a JSON bridge! |
Thanks for the reply. I've just been having issues getting any form of portability working (tried GitLab bridge (even with new dev branch), also tried I do think it would be nice to have a bridge using a protocol that won't break due to uncontrollable changes from external sources (e.g. API changes on third-party platforms), but I understand that this project doesn't have as many contributers as it deserves. |
I'll have to run some tests but this week is pretty busy. I'm thinking the process of using |
Well I got I'm still using the |
JSON files are easier to back up, and also it adds robustness for the situations when |
Hello, I know you're busy and this amazing project is already loaded with things to do. I am just wondering at the feasability of something I would like to do: import a JSON file into a freshly-cloned repo and populate a
git-bug
issue tracker with that data (which would be exported bygit bug ls --format json
). Sort of like a bridge, but with JSON instead of a specific git provider.The background is that I've been having trouble with the bridges, both GitLab (I've tried the dev branch, still having issues), and GitHub (this one I should probably troubleshoot more).
Ultimately, what it comes down to is that I really like the
git-bug
interface, but my issues in dealing with the bridges led me to the realization thatgit-bug
allows you to export the data as JSON. Because I use the issue tracker as a personal to-do list + notepad (and there are no other lightweight TUI programs (that I could find) that match thegit-bug
experience), if I was able to take that exported data and import it into a copy of the repo on another machine, then I would be able to use the awesomegit-bug
interface, with full portability, without any dependence on bridges which could break compatibility at any moment.I hope this idea makes sense, and I hope it could be implemented without too much effort. :)
Thanks
The text was updated successfully, but these errors were encountered: