chore: clean up go feature server docs #5063
Open
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
redhatHameed
approved these changes
Feb 17, 2025
|
@isuyyy can you fix the DCO see the steps here : https://github.com/feast-dev/feast/pull/5063/checks?check_run_id=37323140977 |
isuyyy
force-pushed
the
clean-up-go-feature-server-docs
branch
from
de25de3 to
e38c1e1
Compare
auto-merge was automatically disabled
February 18, 2025 03:56
Head branch was pushed to by a user without write access
isuyyy
force-pushed
the
clean-up-go-feature-server-docs
branch
2 times, most recently
from
72d7673 to
87ab464
Compare
Signed-off-by: isuyyy <[email protected]>
isuyyy
force-pushed
the
clean-up-go-feature-server-docs
branch
from
87ab464 to
436ec3c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Clean up documentation about deploying go feature server using CLI since it is not supported anymore.
Which issue(s) this PR fixes:
relates to #5051
Misc