Closed AZWN closed 8 years ago
Good start! Of all the introduced fields, I think they are best stored in AbstractIssue
itself, even though Pull request do not currently support it, and changing pull requests may not be in the scope of this issue.
Nice to hear :smile:
What would you like as Issue
specific features instead?
I am looking for differences between Github issues and pull requests, and the only difference I seem to find is that one has code and the other doesn't :wink:
So maybe, until we have some good ideas, this class can just be empty! (But we do need it though!)
👍 Tests pass again :)
👍
Looks good so far! :+1:
Whoops, it seems travis handles line breaks somewhat different
I have almost no comments. Lets keep this as-is. You want me to look into adding the comments to the abstracted level and push the result to your branch, or do you see any further problems with that?
What is the status of this branch? :wink: Still writing tests?
Yes, indeed writing tests and fixing styling issues
Ok, I think this feature is quite ready now :smile:
Great work! The IssueBackend
seems to be not necessary right now, but as it is consistent with pull requests, I would keep it as is. I am going to spend this weekend merging PR's and redeploying I think. There is not a real need for changes, but have a look at my comments :wink:
Haha thnx :) I've read your comments. Personally, I like to try and make things as good as possible. This week I don't have time left, but I would like to fix the small issues :D
Ok I'll see whenever your changes arrive
I've adressed some of the issues you pointed out.
Looks very promising on the first sight! Thanks for all the work. Will checkout the branch tonight.
Implementing a basic issue tracker. Still in progress.