WIP: A script for merging a gitea PR #1

Hi!

I started writing the script you asked for.

Hi! I started writing the script you asked for.

well you don't need to put it here but I guess it works for now

Looks ok, I'll test it out when the next PR is up for merging.

It is just a halfway. I also have to check approving the PR and getting the status of checks.

Prerequisites:

the github repo is supposed to be cloned by ssh url
arguments: <gitea username>:<gitea password> <PR no> <github username>:<github access token>

Prerequisites: - the github repo is supposed to be cloned by ssh url - arguments: `<gitea username>:<gitea password> <PR no> <github username>:<github access token>`

You can probably test now on somewhat like Bitmessage/PyBitmessage#4. Currently it only checks github check runs, not all required statuses.

Also I guess opening a PR on github might be done by a buildbot task, triggered by merging a PR here.

You can probably test now on somewhat like https://git.bitmessage.org/Bitmessage/PyBitmessage/pulls/4. Currently it only checks github check runs, not all required statuses. Also I guess opening a PR on github might be done by a buildbot task, triggered by merging a PR here.

I'm now successfully using it, I store the credentials with pass, this allows them to be transparently extracted. There were also some minor changes needed (the repo I'm pushing to / calling API is not derived from my username but it's an organisation). And also some error handling is needed, sometimes the API rates are exceeded as buildbot + code quality + daily clone take a lot of API calls and github refuses to raise the limit for me, they don't even have a paid product that would allow this. But even if there is some temporary error, I can just rerun the script later without having to delete the temporary branches, and it will still work ok.

I'm now successfully using it, I store the credentials with `pass`, this allows them to be transparently extracted. There were also some minor changes needed (the repo I'm pushing to / calling API is not derived from my username but it's an organisation). And also some error handling is needed, sometimes the API rates are exceeded as buildbot + code quality + daily clone take a lot of API calls and github refuses to raise the limit for me, they don't even have a paid product that would allow this. But even if there is some temporary error, I can just rerun the script later without having to delete the temporary branches, and it will still work ok.

Labels Milestones

WIP: A script for merging a gitea PR #1

Reviewers

Step 1:

Step 2: