Failed to build fork private repo (PR) about action-ros-ci HOT 9 OPEN

Can you try the following?

1. Go to https://github.com/$user/$repo/settings/actions (replace $user and $repo). Under "Workflow permissions," select "Read and write permissions." This might already be selected. Not sure why this option would fix this, but you never know.
2. Create your own personal access token and add it as a secret: https://github.com/ros-tooling/action-ros-ci#Use-with-private-repos. If this private repo is under an organisation, you might need to create a special token, I don't remember how that works.

I can give it a try on my end with a private repo, but probably not today.

from action-ros-ci.

Thanks.

I tried "1" , didn't help.
2 is harder since it's an org, and according to action-ros-ci docs is not needed since we do not have private dependencies..
So I would prefer to wait and see your reproduction..

Or if you have other tips that might fix it..

Thanks,
Nir

from action-ros-ci.

2 is harder since it's an org, and according to action-ros-ci docs is not needed since we do not have private dependencies..

Yeah it used to work fine, but these token permissions seem to change all the time 😐

from action-ros-ci.

According to this line :

head means the source repo (which is not the workfile repo)
and base is the target repo.
The action is running againt the target repo and the token is valid for the target repo.

from action-ros-ci.

@timor-raiman FYI

from action-ros-ci.

Good observation.

Sounds like you have two private repos, and you use one as a fork (repo B) and open pull requests against the other one (repo A). Is that correct? My recommendation would be to not fork a private repo, but I guess that doesn't help you much.

Does it work if you use this change then? timor-raiman@c3757c1. I don't think it does (at least not for all cases), because cloning the target repo with a commit hash belonging to the source repo doesn't work.

from action-ros-ci.

Correct, forking the private repo and trying to PR from the fork to the main
@timor-raiman is trying to help with changes to your code..
Hopefully we can find a fix and you can review & merge it..

from action-ros-ci.

Of course, improvements and fixes are always welcome!

from action-ros-ci.

If dirk-thomas/vcstool#258 can be fixed, #816 would resolve this...

from action-ros-ci.