Make Repo.create() use new RepoCreate class for settings - #1095
Conversation
|
@cvrebert Let me find a reviewer for this pull request, thanks for submitting it |
|
@pinaf please review, thanks |
There was a problem hiding this comment.
@cvrebert I'd rather have it named RepoCreate. In the future other actions encoded in json could be RepoDelete, etc
|
@cvrebert even though this PR is rather long, I really like what it does to the code :) |
|
@cvrebert 10 comments above. |
|
@pinaf Responded to all your comments. |
|
@cvrebert thanks. 1 comment above. |
|
@pinaf Done. Addressed that comment. |
|
@yegor256 Please try merging? Hopefully this will have better luck than the other PR. |
|
@yegor256 Please review+merge this. |
|
@rultor try to merge again |
@yegor256 Oops, I failed. You can see the full log here (spent 6min) |
|
@rultor merge again |
|
@yegor256 github error 500 - unrelated |
|
@yegor256 Maybe we could use RetryWire for RtMilestonesITCase since GitHub seems to be flaky on it? |
|
@cvrebert yes, good idea, can you do it in this branch? |
GitHub seems to be frequently giving us HTTP 500 error responses in this testcase.
|
@yegor256 Done. Please retry merge. |
|
@yegor256 Please merge. |
|
@rultor merge |
|
@rultor merge |
|
@rultor deploy now pls |
Fixes #1094 by adding a new parameter class (
NewRepoSettings) and changingRepo.create()to accept an instance of this class as its argument rather than a rawJsonObject.This requires updating a lot of test code since testcases create lots of temporary repos.