Coverage workflow does not support PRs from Forks #179
Comments
jhkennedy
added
CI/CD
fritx
added a commit
to fritx/jsonmerge
that referenced
this issue
Jan 22, 2024
https://github.com/marketplace/actions/git-auto-commit#use-in-forks-from-public-repositories stefanzweifel/git-auto-commit-action#211 https://github.com/orgs/community/discussions/26829#discussioncomment-3253580 winglang/wing#5115 pyiron/actions#44 UffizziCloud/preview-action#80 ASFHyP3/hyp3-isce2#179 tveastman/secateur#54 stm32-rs/stm32-rs#949 actions/gh-actions-cache#73
fritx
added a commit
to Jayin/jsonmerge
that referenced
this issue
Jan 22, 2024
https://github.com/marketplace/actions/git-auto-commit#use-in-forks-from-public-repositories stefanzweifel/git-auto-commit-action#211 https://github.com/orgs/community/discussions/26829#discussioncomment-3253580 winglang/wing#5115 pyiron/actions#44 UffizziCloud/preview-action#80 ASFHyP3/hyp3-isce2#179 tveastman/secateur#54 stm32-rs/stm32-rs#949 actions/gh-actions-cache#73
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jira: https://asfdaac.atlassian.net/browse/TOOL-2507
Note: The above link is accessible only to members of ASF.
Our coverage-report.yml workflow doesn't support PRs from forks b/c it does not have write permissions to a user's fork.
Example: https://github.com/ASFHyP3/hyp3-isce2/actions/runs/7504780261/job/20441454780?pr=177
Ideally, we'd provide a coverage badge that doesn't depend on an image being committed to the repository. But we could either figure out how to get the bot permissions like a maintainer or skip running on forks.
The text was updated successfully, but these errors were encountered: