Different outcome depending on GIT_API_TAGGING is true of false

[maciej-poleszczyk]

Hi,

Scenario.

1. Checkout repo A in . path - this the repo where action is running
2. Checkout repo B into some subfolder - this is the repo in which I want to create new tag
3. Run this action, providing subfolder with repo B, as a SOURCE

Yes, my intention is to create tag in different repo then the one running action.

While using API, it reads old tags from repo B... but tries to create tag in repo A (what fails)
If GIT_API_TAGGING == false, then it creates new tag in repo B - so it behaves as I expect.

Might be that this scenario is not intended to be supported ;-)
My use case is a test/security scan workflow. I'm running actions in repo A, but tests are executed against repo B - to not make a mess in repo running tests and security scans.