chore(ci): Only dry run a release, and only publish github pages, when ci workflow is triggered from main smithy-rs repository #3663
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.
Similar to #3597.
Only run these two workflows when they are triggered from the
smithy-lang/smithy-rs
repository, not from any fork.Motivation and Context
The scheduled dry run fails daily in forks, failing each time, triggering alerts to the owner of the fork repository.
The github pages publishing workflow does not run regularly in forks, but does run when a fork is synced. It would be undesirable for an arbitrary fork to publish.
Description
On each of the two github workflows, add an
if
condition testing the repository owner and name. Only run if it matches the official repository, and is not a fork.Testing
n/a
Checklist
CHANGELOG.next.toml
if I made changes to the smithy-rs codegen or runtime cratesCHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesn/a in both cases
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.