Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

[release-18.0] Change the name of the vitess-tester repository (#16917) #17027

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

vitess-bot[bot]
Copy link
Contributor

@vitess-bot vitess-bot bot commented Oct 22, 2024

Description

This is a backport of #16917

Copy link
Contributor Author

vitess-bot bot commented Oct 22, 2024

Hello @frouioui, there are conflicts in this backport.

Please address them in order to merge this Pull Request. You can execute the snippet below to reset your branch and resolve the conflict manually.

Make sure you replace origin by the name of the vitessio/vitess remote

git fetch --all
gh pr checkout 17027 -R vitessio/vitess
git reset --hard origin/release-18.0
git cherry-pick -m 1 0e22a3e3973cc2e4697e0fdd16128c1bca98b2b1

Copy link
Contributor Author

vitess-bot bot commented Oct 22, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@github-actions github-actions bot added this to the v18.0.8 milestone Oct 22, 2024
@frouioui frouioui force-pushed the backport-16917-to-release-18.0 branch from 36845f5 to f08cb16 Compare November 5, 2024 17:37
@frouioui frouioui removed Skip CI Skip CI actions from running Merge Conflict labels Nov 5, 2024
@frouioui frouioui marked this pull request as ready for review November 5, 2024 17:37
@frouioui frouioui force-pushed the backport-16917-to-release-18.0 branch from f08cb16 to 1dd5d3e Compare November 5, 2024 17:38
@vitess-bot vitess-bot modified the milestones: v18.0.8, v18.0.9 Nov 6, 2024
@frouioui frouioui merged commit 7bc0ef7 into release-18.0 Nov 11, 2024
204 of 205 checks passed
@frouioui frouioui deleted the backport-16917-to-release-18.0 branch November 11, 2024 16:20
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.

3 participants