You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because that PR was based on a fork of dandi-archive, and not a branch internal to the dandi/dandi-archive repo, the DOCKER_LOGIN and DOCKER_TOKEN GitHub Actions secrets could not be read due to permission issues.
The text was updated successfully, but these errors were encountered:
I think this could be the only solution (may be besides also adding retries in addition)
to allow testing against dandi-cli to be done also in PRs from forks of the project,
where there is no credentials. We could also advise our developers to provide such (own)
credentials in their forks.
FTR: login originally was added in 6b815dc
ref: dandi#2107
yarikoptic
added a commit
to yarikoptic/dandi-archive
that referenced
this issue
Dec 19, 2024
I think this could be the only solution (may be besides also adding retries in addition)
to allow testing against dandi-cli to be done also in PRs from forks of the project,
where there is no credentials. We could also advise our developers to provide such (own)
credentials in their forks.
FTR: login originally was added in 6b815dc
ref: dandi#2107
Example: #2105
Because that PR was based on a fork of
dandi-archive
, and not a branch internal to thedandi/dandi-archive
repo, theDOCKER_LOGIN
andDOCKER_TOKEN
GitHub Actions secrets could not be read due to permission issues.The text was updated successfully, but these errors were encountered: