Skip to content

Conversation

@ftnext
Copy link
Contributor

@ftnext ftnext commented Jan 1, 2026

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:

  • 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

  • I have read the CONTRIBUTING.md document.
  • I have performed a self-review of my own code.
  • 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.

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.
@google-cla
Copy link

google-cla bot commented Jan 1, 2026

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.

@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@adk-bot
Copy link
Collaborator

adk-bot commented Jan 1, 2026

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!

@adk-bot adk-bot added the tools [Component] This issue is related to tools label Jan 1, 2026
@ftnext
Copy link
Contributor Author

ftnext commented Jan 1, 2026

It seems Claude Code's commit doesn't pass CLA Action.
I'll retry
-> #4059

@ftnext ftnext closed this Jan 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tools [Component] This issue is related to tools

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workflow fails when automatically executed on forks

3 participants