Disable scheduled GitHub Actions workflows in forks#4058
Disable scheduled GitHub Actions workflows in forks#4058ftnext wants to merge 1 commit intogoogle:mainfrom
Conversation
Add repository checks to prevent scheduled workflows from running in forked repositories. This prevents excessive notifications from periodic workflow runs (every 6 hours for triage, daily for stale-bot and docs upload) in forks where they are not needed. The workflows will now only run in the main google/adk-python repository.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Response from ADK Triaging Agent Hello @ftnext, thank you for creating this PR! Before we can merge your contribution, you'll need to sign a Contributor License Agreement (CLA). You can do so by following the instructions at https://cla.developers.google.com/. Thanks! |
|
It seems Claude Code's commit doesn't pass CLA Action. |
Link to Issue or Description of Change
1. Link to an existing issue (if applicable):
Problem:
Excessive notifications from periodic workflow runs (every 6 hours for triage, daily for stale-bot and docs upload) in forks where they are not needed.
Solution:
Add repository checks to prevent scheduled workflows from running in forked repositories.
The workflows will now only run in the main google/adk-python repository.
Testing Plan
I think that unit tests and E2E are not needed because this change is for GitHub Actions (not ADK source code).
Please describe the tests that you ran to verify your changes. This is required
for all PRs that are not small documentation or typo fixes.
Unit Tests:
Please include a summary of passed
pytestresults.Manual End-to-End (E2E) Tests:
Please provide instructions on how to manually test your changes, including any
necessary setup or configuration. Please provide logs or screenshots to help
reviewers better understand the fix.
Checklist