Get enterprise modules if secret is available instead of always skipping on forks.#7118
Get enterprise modules if secret is available instead of always skipping on forks.#7118bmarty wants to merge 5 commits into
Conversation
|
📱 Scan the QR code below to install the build (arm64 only) for this PR. |
As per the doc https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets#using-secrets-in-a-workflow says: `Secrets cannot be directly referenced in if: conditionals`
13e065e to
da85c5f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #7118 +/- ##
========================================
Coverage 80.54% 80.54%
========================================
Files 2689 2689
Lines 76433 76433
Branches 10291 10291
========================================
Hits 61566 61566
Misses 10933 10933
Partials 3934 3934 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This PR is now OK, but a PR from a fork which have the expected secret (on their side) cannot use it. It seems that the secret is not shared with upstream, which actually makes sense. See |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|




Content
Get enterprise modules if secret is available instead of always skipping on forks.
Motivation and context
Let forks that have a deploy key secret be able to build enterprise application.
Screenshots / GIFs
NA
Tests
Tested devices
Checklist