This is half of fedrepo_req#129.
Whenever a user requests a non-standard branch, we will also submit a request for a matching module with matching stream and matching SLs.
In a subsequent changeset, we want to make the admin tool automatically populate new module repos with a useful modulemd starter template.
Should s/not//?
s/not//
Run command fedpkg-stage --module-name testrepo request-branch some-version --sl "security_fixes:2020-12-01", three issues are created:
fedpkg-stage --module-name testrepo request-branch some-version --sl "security_fixes:2020-12-01"
Is this result expected?
I get the answer from the test in test_cli.py. It's yes.
test_cli.py
All these issues have same id 2. Would it be good to use three different ids to represent different issues?
2
It would be good to write a docstring for _request_repo and _request_branch to describe method and arguments.
_request_repo
_request_branch
It would be ... but, it's just an artifact of the mocking. I didn't dig into see how difficult it would be to change and have a different value for each.
rebased onto 56080f9d0e53602b65638401faa79840cfa9feb7
5 new commits added
OK, @cqi, all of your comments should be addressed at this point. Can you give this a second round of review?
Looks good to me. :thumbsup: Thanks @ralph
Looks good to me too.
Pull-Request has been merged by cqi
This is half of fedrepo_req#129.
Whenever a user requests a non-standard branch, we will also submit a request for a matching module with matching stream and matching SLs.
In a subsequent changeset, we want to make the admin tool automatically populate new module repos with a useful modulemd starter template.