Walletwasabi: Fix GitHub Actions

[nopara73]

@molnard https://github.com/zkSNACKs/WalletWasabi/pull/2321 Ruined our ability to keep our master up to date.

 ! [remote rejected]   master -> master (refusing to allow an integration to create or update .github/workflows/ci.yml)
error: failed to push some refs to 'https://github.com/nopara73/WalletWasabi.git'

I'd prefer it to be fixed ASAP, but if not, I revert with PR https://github.com/zkSNACKs/WalletWasabi/pull/2328

[molnard]

Let me see, wait a minute.

[molnard]

@nopara73 are you doing this (create or update .github/workflows/ci.yml) actually? Or is it just bugged in some way?

[molnard]

I figured it out... It is non-intuitive but you must do git rm .github/main.workflow before you can git push even if your push does not modify the file .github/main.workflow in any way. This means that a push to upstream must kill the Action until the upstream user manually adds it once again.

Solution for now:

This isn't just for deleting main.workflow, it also happens when it's being modified. Same problem with Git Kraken. The only solution I found is to use the git command line or edit/delete the file on github.com. Adding /.github/main.workflow to .gitignore helps but there's still a problem when merging a branch to another branch with changes to the workflow file. I would love to see a proper solution though.

Discussion here:
https://github.com/desktop/desktop/issues/6526#issuecomment-450990880

[molnard]

Ok, I made some investigations. So can you try to switch to a git URL over an HTTP URL for git?

It works for me.

[molnard]

Changing to git URL (SSH) is not an option as it makes the contributions hard.

[molnard]

Asked the question here, waiting for the answer: https://github.community/t5/GitHub-Actions/Refusing-to-allow-an-integration-to-create-or-update/m-p/32472#M1146

[yahiheb]

@molnard Have you seen this https://github.community/t5/GitHub-Actions/Refusing-to-allow-an-integration-to-create-or-update/m-p/41365/highlight/true#M4593

[nopara73]

@yahiheb That doesn't help. That's a client side hack, we cannot expect every contributor of Wasabi to figure that out.

[molnard]

Yes, I have seen that. They won't solve it - it is by design. You cannot use https as a remote if GitHub action files are there - for security reasons.
We will stick with Azure regarding CI - it is evolving faster and better.