git | Package git provides an incomplete pure Go implementation

If anyone help me understand whether my-branch will be matched with the remote one or not

Probably. But it's impossible to be certain from the info you have given. To find out, say

be aware I don't have a Windows machine against which to try this, so it's just "best effort"

As best I can tell, your problem is because you are trying to recreate the behavior of win_shell by "manually" invoking that improperly quoted cmd.exe /c business, ending up with cmd.exe /c "cmd.exe /c whatever"; dialing up the ansible verbosity -vv could confirm or deny that pattern

Also, the win_shell docs say to use win_command: unless you have a shell redirect need, which as written your task does not.

The "GitHub" extension in question should be the microsoft/vscode-pull-request-github, which, in its issues, does not mention anything about active and unknown at all.

I just tested on my VSCode 1.57, and clicking on that link does work.

Try and disable other plugins installed to see if one might cause the issue.

The OP JimBoyLim confirms in the comments:

I finally just reinstalled VSCode, and now its working!

Try to clone it with the URL and not via SSH

Ok, this should work. Remove the last line - run: git push from your action. Then add the following.

" It sounds as if rebasing "replays" commits, one after another (so sequentially) from the source branch over the changes in my working branch, is this the case? "

Yes.

" Furthermore, it does so, one develop commit at a time, until all the changes have been "replayed" into my feature branch, yes? "

No, it's the contrary. If you rebase your branch on origin/develop, all your branch's commits are to be replayed on top of origin/develop, not the other way around.

Finally, the difference between merge and rebase scenarios has been described in details everywhere, including on this site, but very broadly the merge workflow will add a merge commit to history. For that last part, take a look here for a start.

The Git configuration of user.name and user.email has nothing to do with the permission error. You can specify any email and username. Those two values goes only into the commit author information.

The real issue that you are facing is that you need two different github accounts. Your machine caches the first github account and uses that one to authenticate against the repository where the cached credentials does not have access permissions.

There are two possible solutions to face this issue:

• Use SSH keys and clone the repositories using ssh
• Grant the other account access to the non working repository

I would prefer the first one.

This is a job that xargs is created to fix -- splitting lists of items into individual command lines that are within the permitted limit.

Because running jq -s a single time is different from concatenating the results of multiple smaller runs, it's appropriate to use xargs to combine cat invocations using the manner described in the linked duplicate.

Yes. Depending on if the other branches have new commits:

1. If the other branches have new commits of their own, simply check each one out and git rebase origin/master.
2. If the other branches don't have new commits of their own, while on a branch you wish to duplicate, you can just re-create the others with git branch -f branchDothis, etc. for each branch. Note you could delete them and recreate them, or use the -f flag which mean "force create even if it already exists". The end result is the same.