Skip to content

Conversation

@biergaizi
Copy link
Contributor

@biergaizi biergaizi commented Jan 23, 2026

CI: skip default branch when resolving dependencies.

The dependency resolution logic resolve_dependent_repos.py currently tries to apply the "ganged branch" logic even for the default branch, creating useless and misleading warnings:

* thliebig/CSXCAD: different branch "master" used
  repo thliebig/CSXCAD branch master is used instead of the default branch.

* thliebig/fparser: different branch "master" used
  repo thliebig/fparser branch master is used instead of the default branch.

Avoid applying "branch ganging" if the dependency is already on the branch we're switching to.

CI: remove unused "permissions: packages: write"

The option permissions: packages: write was used to enable NuGet repository for vcpkg caching, but eventually this caching method was not used due to my security concerns of cache poisoning. It's unclear whether a third-party contributor can write arbitrary packages to the NuGet repository. Thus, regular GitHub file caching via "actions/cache" was used (which is isolated per branch, by default, it's not possible to overwrite the trusted "master" branch caching just by opening a PR).

Remove unused permissions: packages: write.

The dependency resolution logic resolve_dependent_repos.py currently
tries to apply the "ganged branch" logic even for the default branch,
creating useless and misleading warnings:

    * thliebig/CSXCAD: different branch "master" used
      repo thliebig/CSXCAD branch master is used instead of the default branch.

    * thliebig/fparser: different branch "master" used
      repo thliebig/fparser branch master is used instead of the default branch.

Avoid applying "branch ganging" if the dependency is already on the
branch we're switching to.

Signed-off-by: Yifeng Li <tomli@tomli.me>
@biergaizi biergaizi changed the title CI: fix useless warning, skip default branch when resolving dependencies. CI: fix useless warnings, skip default branch when resolving dependencies. Jan 23, 2026
The option "permissions: packages: write" was used to enable NuGet
repository for vcpkg caching, but eventually this caching method
was not used due to my security concerns of cache poisoning. It's
unclear whether a third-party contributor can write arbitrary
packages to the NuGet repository. Thus, regular GitHub file caching
via "actions/cache" was used (which is isolated per branch, by
default, it's not possible to overwrite the trusted "master" branch
caching just by opening a PR).

Remove unused "permissions: packages: write".

Signed-off-by: Yifeng Li <tomli@tomli.me>
@biergaizi biergaizi force-pushed the dependent_repos_skip branch from 7c01582 to e96d9d3 Compare January 25, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant