We would like to move couple of repositories from Pagure to GitHub:
The main problems with Pagure repositories:
The repositories on already have a GitHub mirror to enable automated Quay builds and building docs on readthedocs.org (for waiverdb and greenwave):
Greenwave also uses GitHub actions but it is not connected to Pagure PRs in any way. PRs on GitHub show CI status and block on failure.
@jskladan, @frantisekz, @tflink Does it sound good from your side?
I can also set you as maintainers of the new resultsdb repos if you are interested.
Fine with me. I don't really care that much about where the project is hosted. Sounds like I should create a RH github account :D
Sounds like I should create a RH github account :D
Hmm, that's a good point. :)
I use my public account for RH repos too. It could be a bit confusing to see other mail in git commits. Also, notifications for the new repos would go into my public mail address.
Can you help review https://github.com/release-engineering/resultsdb/pull/1 ?
Yet another PR: https://github.com/release-engineering/resultsdb/pull/4
Can you disable the synchronization to github (in resultsdb_frontend too)? Looks like it caused the branch in PR to be deleted. I will drop pagure permission on github for now.
I've disabled the synchronization on GitHub side (removed permission for Pagure).
Can someone also change description in this project so it redirects people to https://github.com/release-engineering/resultsdb ?
I kinda prefer Pagure for being open source, and CI on Pagure is not actually that difficult to set up - I use that setup for multiple projects and it works fine. But I can live with github if necessary.
We have some big changes planned for ResultsDB:
Any reviews and suggestions are welcome!
Log in to comment on this ticket.