Skip to content

Don't run tests after a PR is merged#1657

Merged
copybara-service[bot] merged 1 commit into
mainfrom
no_push_tests
May 1, 2025
Merged

Don't run tests after a PR is merged#1657
copybara-service[bot] merged 1 commit into
mainfrom
no_push_tests

Conversation

@shralex

@shralex shralex commented Apr 30, 2025

Copy link
Copy Markdown
Collaborator

Currently, once Github tests pass and the PR merges in our Google repo, our workflow merges the PR in Github. Then, after the merge, tests are again triggered in Github on the main branch. We already have regular scheduled tests on main, so this isn't needed.

Checklist

Before submitting this PR, please make sure (put X in square brackets):

  • I have performed a self-review of my code.
  • I have necessary comments in my code, particularly in hard-to-understand areas.
  • I have run end-to-end tests tests and provided workload links above if applicable.
  • I have made or will make corresponding changes to the doc if needed.

@richjames0 richjames0 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

lgtm

Currently, once Github tests pass and the PR merges in our Google repo,
our workflow merges the PR in Github. Then, after the merge, tests are
again triggered in Github on the main branch. We already have regular
scheduled tests on main, so this isn't needed.
@copybara-service copybara-service Bot merged commit 1efc736 into main May 1, 2025
@copybara-service copybara-service Bot deleted the no_push_tests branch May 1, 2025 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants