Skip to content

ci: reduce workflow failures on forks#3176

Merged
marvinhagemeister merged 1 commit intodenoland:mainfrom
csvn:ci/fork-workflow-failures
Aug 1, 2025
Merged

ci: reduce workflow failures on forks#3176
marvinhagemeister merged 1 commit intodenoland:mainfrom
csvn:ci/fork-workflow-failures

Conversation

@csvn
Copy link
Contributor

@csvn csvn commented Aug 1, 2025

Publishing packages workflow and deploying to Deno Deploy step runs even for forks. This is annoying, since it creates some spam every push for any open PR's.

This PR tries to address this, by skipping certain steps or workflows unless the current GitHub org is denoland, which should be pretty safe long term.

Failed workflow spam

image image

Copy link
Collaborator

@marvinhagemeister marvinhagemeister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Admittedly I never looked at that tab before. Great idea on ensuring that we're on top of that!

@marvinhagemeister marvinhagemeister merged commit 2e68c30 into denoland:main Aug 1, 2025
7 checks passed
@csvn csvn deleted the ci/fork-workflow-failures branch August 1, 2025 18:45
@csvn
Copy link
Contributor Author

csvn commented Aug 1, 2025

Sweet! Just synced my fork after merging this, and everything's green! 👍

image

csvn added a commit to csvn/fresh that referenced this pull request Aug 2, 2025
Publishing packages workflow and deploying to Deno Deploy step runs even
for forks. This is annoying, since it creates some spam every push for
any open PR's.

This PR tries to address this, by skipping certain steps or workflows
unless the current GitHub org is `denoland`, which should be pretty safe
long term.

## Failed workflow spam

<img width="1396" height="635" alt="image"
src="https://github.com/user-attachments/assets/d939d1f5-e736-42a4-9355-f946b3d6ddf2"
/>

<img width="1577" height="905" alt="image"
src="https://github.com/user-attachments/assets/fbf7ffe3-2759-430a-a33e-c8de0d7e113c"
/>
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.

2 participants