-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check for secrets being present at GitHub workflows #5973
Conversation
Does not work that simple. Solution proposal: https://gh.neting.ccmunity/t5/GitHub-Actions/If-expression-with-context-variable/td-p/34556 |
b8ef7b7
to
21c6e5e
Compare
78d2507
to
27ba8c0
Compare
5cb31af
to
80594a1
Compare
The issue of secrets not available to forks is known to GitHub folks, but no concrete activity announced: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit unfortunate that apparently there is no easier solution...
* upstream/master: Fix image path Check for secrets being present at GitHub workflows (#5973) Add "JabRef and Software Engineering" Make Java code acceptable for GitBook - and fix link to JUnit antipatterns Let "Contributing" be displayed Merge the reviewing steops of "Code Quality" to "Development Strategy" Try to include CONTRIBUTING.md in devdocs.jabref.org Minor improvments in CONTRIBUTING.md Update Codecov yaml with proper indentation (#6156) Complete refactor of LibraryProperties to mvvm (#6107) Try comment:false Remove duplicated line Fix: Only if `.sav` file has changes a recovery dialog is shown (#6116) Fix formatting for GitBook Add hint to scroll down
When an external PR (e.g., #5967) comes in, our secrets are not known to that PR. Thus, all external PRs fail. With this PR, the workflow jobs requiring credentials are skipped.
Depends on #6145.