WIP: Pinpoint some of the reasons for bug #385

Work in progress. The github bridge contains a bug documented in issue #385.
This commit shows what is the problem. There might be more problems. I have
changed the GraphQL query for timeline items and there are much less wrong
imports now. (Are there any malformed imports left?) I would like to rework the
entire bridge/github/iterator in the near future in order to create a reliable
fix for this bug.

1 files changed, 19 insertions, 3 deletions

diff --git a/bridge/github/import_query.go b/bridge/github/import_query.go
index 58f6d95e..264f5c22 100644
--- a/bridge/github/import_query.go
+++ b/bridge/github/import_query.go
@@ -98,9 +98,10 @@ type timelineItem struct {
 
 type issueTimeline struct {
 	authorEvent
-	Title string
-	Body  githubv4.String
-	Url   githubv4.URI
+	Title  string
+	Number githubv4.Int
+	Body   githubv4.String
+	Url    githubv4.URI
 
 	TimelineItems struct {
 		Edges []struct {
@@ -116,6 +117,21 @@ type issueTimeline struct {
 	} `graphql:"userContentEdits(last: $issueEditLast, before: $issueEditBefore)"`
 }
 
+// Alex
+type timelineItemsQuery struct {
+	Repository struct {
+		Issue struct {
+			TimelineItems struct {
+				Edges []struct {
+					Cursor githubv4.String
+					Node timelineItem
+				}
+				PageInfo pageInfo
+			} `graphql:"timelineItems(first: $timelineFirst, after: $timelineAfter)"`
+		} `graphql:"issue(number: $issueNumber)"`
+	} `graphql:"repository(owner: $owner, name: $name)"`
+}
+
 type issueEdit struct {
 	UserContentEdits struct {
 		Nodes    []userContentEdit