Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Actually fail if staleness fail #15984

Conversation

mkruskal-google
Copy link
Member

PiperOrigin-RevId: 610833812

PiperOrigin-RevId: 610833812
@mkruskal-google mkruskal-google added the back-port Cherrypick PRs to release branches label Feb 27, 2024
@mkruskal-google mkruskal-google requested a review from a team as a code owner February 27, 2024 21:36
@mkruskal-google mkruskal-google requested review from zhangskz and removed request for a team February 27, 2024 21:36
@mkruskal-google mkruskal-google changed the base branch from 25.x to staleness-fix-25 February 27, 2024 21:39
@zhangskz
Copy link
Member

Maybe push to dev branch in protocolbuffers so test can actually run? (although I think you tested this already though)

Sidenote: I thought we supposedly exempted ourselves from the "safe for tests" requirement?

@mkruskal-google
Copy link
Member Author

Nope, our forks aren't exempt. And this actually won't run tests from a fork because I touched workflows, changed the base

@mkruskal-google mkruskal-google requested review from a team as code owners February 27, 2024 21:43
@mkruskal-google mkruskal-google requested review from JasonLunn and removed request for a team February 27, 2024 21:43
@mkruskal-google mkruskal-google merged commit 489aba5 into protocolbuffers:staleness-fix-25 Feb 27, 2024
1 check passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
back-port Cherrypick PRs to release branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants