Skip to content
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

ci(check): fail CI wih ci/force-publish label on PRs from forks (backport of #9801) #9803

Closed
wants to merge 1 commit into from

Conversation

kumahq[bot]
Copy link
Contributor

@kumahq kumahq bot commented Apr 3, 2024

Automatic cherry-pick of #9801 for branch release-2.3

Generated by action

cherry-picked commit 361ca95
⚠️ ⚠️ ⚠️ Conflicts happened when cherry-picking! ⚠️ ⚠️ ⚠️

On branch release-2.3
Your branch is up to date with 'origin/release-2.3'.

You are currently cherry-picking commit 361ca951d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .github/workflows/build-test-distribute.yaml

no changes added to commit (use "git add" and/or "git commit -a")

)

There is no access to secrets on a PRs from forks, so to have
a quick feedback, whole workflow will immediately fail when
CI will detect `ci/force-publish` label on such PRs.

Signed-off-by: Bart Smykla <[email protected]>
@bartsmykla bartsmykla closed this Apr 3, 2024
@bartsmykla bartsmykla deleted the chore/backport-release-2.3-9801 branch April 3, 2024 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant