This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
Restore search endpoint #372
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remi-dupre
force-pushed
the
restore-search-endpoint
branch
from
21b3edc to
d3e1276
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Obtained by a
git cherry-pick f9448d25004c41472c9c0f8b7b901bc1c0aa8726There is a diff with master after this operation (~10 changes) so my job now would be to check if it needs to be solved in this branch or in #370
NOTE: Github shows a huge diff with master but I don't get why yet, on my machine the diff is very short when I run
git diff restore-search-endpoint master(maybe because of the conflicts 🤷)