Skip to content

Stop reporting missing endpoints as errors #4031

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

Merged
merged 1 commit into from
Mar 24, 2025

Conversation

pquentin
Copy link
Member

We have other ways of identifying them.

We have other ways of identifying them.
@pquentin pquentin requested a review from a team as a code owner March 19, 2025 07:46
@pquentin pquentin requested a review from swallez March 19, 2025 07:47
Copy link
Member

@swallez swallez left a comment

Choose a reason for hiding this comment

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

LGTM

@pquentin pquentin merged commit f7edcb5 into main Mar 24, 2025
16 checks passed
@pquentin pquentin deleted the stop-reporting-missing-endpoitns branch March 24, 2025 10:01
Copy link
Contributor

The backport to 8.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.x 8.x
# Navigate to the new working tree
cd .worktrees/backport-8.x
# Create a new branch
git switch --create backport-4031-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f7edcb5e57a5d17ca7a7ab30662b7c8d0b8ee19e
# Push it to GitHub
git push --set-upstream origin backport-4031-to-8.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.x

Then, create a pull request where the base branch is 8.x and the compare/head branch is backport-4031-to-8.x.

Copy link
Contributor

The backport to 8.18 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.18 8.18
# Navigate to the new working tree
cd .worktrees/backport-8.18
# Create a new branch
git switch --create backport-4031-to-8.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 f7edcb5e57a5d17ca7a7ab30662b7c8d0b8ee19e
# Push it to GitHub
git push --set-upstream origin backport-4031-to-8.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.18

Then, create a pull request where the base branch is 8.18 and the compare/head branch is backport-4031-to-8.18.

github-actions bot pushed a commit that referenced this pull request Mar 24, 2025
We have other ways of identifying them.

(cherry picked from commit f7edcb5)
pquentin added a commit that referenced this pull request Mar 24, 2025
We have other ways of identifying them.

(cherry picked from commit f7edcb5)

Co-authored-by: Quentin Pradet <[email protected]>
pquentin added a commit that referenced this pull request Mar 24, 2025
We have other ways of identifying them.

(cherry picked from commit f7edcb5)

# Conflicts:
#	output/schema/validation-errors.json
pquentin added a commit that referenced this pull request Mar 24, 2025
We have other ways of identifying them.

(cherry picked from commit f7edcb5)

# Conflicts:
#	output/schema/validation-errors.json
@pquentin
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
8.x
8.18

Questions ?

Please refer to the Backport tool documentation

pquentin added a commit that referenced this pull request Mar 24, 2025
We have other ways of identifying them.

(cherry picked from commit f7edcb5)

# Conflicts:
#	output/schema/validation-errors.json
pquentin added a commit that referenced this pull request Mar 24, 2025
We have other ways of identifying them.

(cherry picked from commit f7edcb5)

# Conflicts:
#	output/schema/validation-errors.json
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.

2 participants