Skip to content

CLI Export Command #45

Closed
Closed

Description

@andyl

In #5 @MichaelMure settled on JSON as a serialization format.

Feature request: add a CLI command to export the issue repository.

Something like: git bug export that just exports the whole issue repo as JSON would be great.

Activity

  1. MichaelMure commented on Sep 14, 2018

    @MichaelMure
    Contributor

    Alright, a few questions:

    • 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.

  2. andyl commented on Sep 14, 2018

    @andyl
    Author

    I need a current snapshot which returns all issues in the repo. Don't need the commit history.

    For each issue:

    • some sort of unique issue ID
    • title, description, status, labels
    • comments
  3. MichaelMure commented on Sep 14, 2018

    @MichaelMure
    Contributor

    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.

  4. andyl commented on Sep 14, 2018

    @andyl
    Author

    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.

  5. MichaelMure commented on Sep 14, 2018

    @MichaelMure
    Contributor

    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.

  6. MichaelMure commented on May 23, 2020

    @MichaelMure
    Contributor

    Closing in favor of #392

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions