feat(drone-sig): add check for fork #695
Open
+36
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zzehring
force-pushed
the
zzehring/check-drone-sig/add-fork-awareness
branch
from
4347828 to
b2361f1
Compare
Since this reusable workflow is used by OSS projects, we need to be aware if we're dealing with a fork or not, especially when it comes to PRs. If we're on a fork, we don't have access to the secret needed to run the drone ci config signature validation. In this case, we post a comment to the PR saying we're skipping the check and someone with proper repo persmissions needs to check/sign the drone ci config changes.
zzehring
force-pushed
the
zzehring/check-drone-sig/add-fork-awareness
branch
from
b2361f1 to
71dfdb9
Compare
zerok
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since this reusable workflow is used by OSS projects, we need to be aware if we're dealing with a fork or not, especially when it comes to PRs. If we're on a fork, we don't have access to the secret needed to run the drone ci config signature validation. In this case, we post a comment to the PR saying we're skipping the check and someone with proper repo persmissions needs to check/sign the drone ci config changes.