Skip to content

chore: remove retired OwlBot and legacy bot configs - #9911

Open
quirogas wants to merge 1 commit into
googleapis:mainfrom
quirogas:chore/remove-retired-bot-configs
Open

quirogas wants to merge 1 commit into
googleapis:mainfrom
quirogas:chore/remove-retired-bot-configs

Conversation

@quirogas

Copy link
Copy Markdown
Contributor

Description

Removes obsolete bot configuration files and retired OwlBot entries.

Impact

Keeps repository automation configs aligned with active monorepo tooling.

Changes

  • Delete .github/auto-approve.yml (NodeDependency only matches package.json-only diffs and never approves pnpm-lock.yaml pull requests).
  • Delete .github/release-trigger.yml (superseded by tag-driven release automation).
  • Remove retired gcf-owl-bot[bot] and owlbot-bootstrapper[bot] from .github/trusted-contribution.yml.
  • Remove duplicate top-level keys in .github/release-please.yml already defined on each branches entry.

Testing

  • Validated YAML syntax for .github/trusted-contribution.yml and .github/release-please.yml.
  • Verified no workflows or scripts reference .github/auto-approve.yml or .github/release-trigger.yml.

Alternatives

  • Retaining unused bot configurations leaves stale OwlBot and pre-pnpm rules in .github/.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request cleans up configuration files by removing obsolete files, removing OwlBot-related bots from the trusted contributors list, and refactoring the .github/release-please.yml configuration. However, removing the top-level manifest and tagPullRequestNumber keys from .github/release-please.yml will cause the main branch to lose these configurations. It is recommended to explicitly add these settings to the main branch configuration block to preserve the intended behavior.

Comment on lines 1 to 3
branches:
- branch: main
handleGHRelease: true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The top-level keys manifest: true and tagPullRequestNumber: true were removed under the assumption that they are already defined on each branch entry. However, the main branch entry does not define them. Removing them globally will cause the main branch to lose these configurations. Please add them to the main branch entry to preserve the existing behavior.

branches:
  - branch: main
    handleGHRelease: true
    manifest: true
    tagPullRequestNumber: true

@quirogas
quirogas marked this pull request as ready for review November 19, 2026 21:17
@quirogas
quirogas requested a review from a team as a code owner November 19, 2026 21:17
@github-actions
github-actions Bot requested a review from shivanee-p November 19, 2026 21:17
@quirogas
quirogas enabled auto-merge (squash) November 19, 2026 21:18

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant