snuyanzin opened a new pull request, #26864: URL: https://github.com/apache/flink/pull/26864
## What is the purpose of the change The problem is that if someone syncs his/her fork with recent master then stale PR and community review process will start running on that fork as well... and sometimes will start spam to email about failures for instance failures on my fork https://github.com/snuyanzin/flink/actions/workflows/community-review.yml The PR makes it not running stale PRs and community review process only for forks in similar way it is done for flink connectors like https://github.com/apache/flink-connector-kafka/blob/ecedd632bbf86d333f376374d4674e79e2f614b8/.github/workflows/weekly.yml#L29 ## Brief change log GH actions ## Verifying this change manually or sync your master with this and force run action ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): ( no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: ( no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): ( no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: ( no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? ( no) - If yes, how is the feature documented? (not applicable) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
