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
do you need the data of a single bug or the repo as a whole ?
do you need the compiled state of the bug or the history as well ?
I may keep git bug import/git bug export for the bridge operation with external bug trackers, but this feature might be added as a flag of git bug show for example.
Does it have to be the whole repo in one go or could it be exporting bugs individually and a way to iterate them ?
I'm thinking of doing something similar to git for-each-ref and having a command return a list of ids corresponding to a query, while another command would export a bug state a JSON. That would make the pieces reusable and combinable in various scenario.
Does it have to be the whole repo in one go or could it be exporting bugs individually and a way to iterate them ?
Either would be fine.
I'm thinking of doing something similar to git for-each-ref and having a command return a list of ids corresponding to a query, while another command would export a bug state a JSON. That would make the pieces reusable and combinable in various scenario.
That would be great. If you could query on 'last-change-date' then we could avoid a lot of wasted bandwidth.
Just a note, if you care about the bandwidth, you would be better at using git bug pull to get the delta since the last sync as compressed blob and query bugs locally.
Activity
MichaelMure commentedon Sep 14, 2018
Alright, a few questions:
I may keep
git bug import/git bug exportfor the bridge operation with external bug trackers, but this feature might be added as a flag ofgit bug showfor example.andyl commentedon Sep 14, 2018
I need a current snapshot which returns all issues in the repo. Don't need the commit history.
For each issue:
MichaelMure commentedon Sep 14, 2018
Does it have to be the whole repo in one go or could it be exporting bugs individually and a way to iterate them ?
I'm thinking of doing something similar to
git for-each-refand having a command return a list of ids corresponding to a query, while another command would export a bug state a JSON. That would make the pieces reusable and combinable in various scenario.andyl commentedon Sep 14, 2018
Either would be fine.
That would be great. If you could query on 'last-change-date' then we could avoid a lot of wasted bandwidth.
MichaelMure commentedon Sep 14, 2018
Just a note, if you care about the bandwidth, you would be better at using
git bug pullto get the delta since the last sync as compressed blob and query bugs locally.MichaelMure commentedon May 23, 2020
Closing in favor of #392