Disable scheduled GitHub Actions workflows in forks #4059
Closed
+7
−3
Conversation
This file contains hidden or 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
Contributor
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
9 tasks
Collaborator
|
Hi @ftnext , Thank you for your contribution! We appreciate you taking the time to submit this pull request. |
Collaborator
|
Hi @wuliang229 , can you please review this. LGTM. |
ryanaiagent
added
the
needs-review
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.
wuliang229
force-pushed
the
disable-fork-actions
branch
from
b1858aa to
991cc94
Compare
wuliang229
approved these changes
Jan 15, 2026
wuliang229
added
the
ready to pull
copybara-service bot
pushed a commit
that referenced
this pull request
Jan 15, 2026
Merge #4059 ### Link to Issue or Description of Change **1. Link to an existing issue (if applicable):** - Closes: #3961 **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:** - [ ] I have added or updated unit tests for my change. - [ ] All unit tests pass locally. _Please include a summary of passed `pytest` results._ **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 - [x] I have read the [CONTRIBUTING.md](https://github.com/google/adk-python/blob/main/CONTRIBUTING.md) document. - [x] I have performed a self-review of my own code. - [x] I have commented my code, particularly in hard-to-understand areas. - [ ] I have added tests that prove my fix is effective or that my feature works. - [ ] New and existing unit tests pass locally with my changes. - [ ] I have manually tested my changes end-to-end. - [ ] Any dependent changes have been merged and published in downstream modules. COPYBARA_INTEGRATE_REVIEW=#4059 from ftnext:disable-fork-actions 991cc94 PiperOrigin-RevId: 856691019
Collaborator
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
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