Skip to content

Initial Extraction use case #2

@fenwickjb

Description

@fenwickjb

The selection subsystem will send to us a single repo URL. Our job will be to dig into the repo, collecting data. We will return everything we find as a complex web of objects rooted as a Repository object. Initially, we need at least the Repository object (maybe nothing else yet). Initially, the Repository object should have some useful data items in it that we fill. Note we just build the Repository object and give it back; that client does something with it. But we can still have a demo that "mocks" a client to supply a test repo and print out our Repository object.

Some other anticipated objects are: Collaborator, Organization, PullRequest, Commit, Comment, Issue.

All of these objects will have various attributes that supply information about them. For example, a Commit object may have a field that indicates the Collaborator that created the issue.

Metadata

Metadata

Labels

epicA big story (that needs breaking down)extractionBelongs to extraction

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions