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

feat(docs): added FAQ question for AVS deregistration #2808

Merged
merged 2 commits into from
Jan 21, 2025

Conversation

Zodomo
Copy link
Contributor

@Zodomo Zodomo commented Jan 15, 2025

Added a FAQ question providing info about how to deregister from the AVS.

issue: #601

@Zodomo Zodomo requested review from ttarsi and fabtreb January 15, 2025 17:12
@Zodomo Zodomo self-assigned this Jan 15, 2025
Copy link

Docs preview complete 🚀 see it here: https://omni-lkgkkcmwl-omni-engineering.vercel.app

Copy link
Contributor

@ttarsi ttarsi left a comment

Choose a reason for hiding this comment

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

Approving with some change requests. I think we can make this much simpler – with these instructions, they'll need to infer that they have to build from source, copy the commit, check it out, learn the command to build from source, etc. Let's make it simpler.

"To deregister, you need to build the CLI from source using main:

git clone <repo>
cd <repo>
go install <whatever the command is>
omni operator deregister <path>

"

Make it as simple as possible. Operators are smart but they're not protocol devs

Copy link

Docs preview complete 🚀 see it here: https://omni-q46o13p0m-omni-engineering.vercel.app

@Zodomo Zodomo merged commit e776d9f into main Jan 21, 2025
21 checks passed
@Zodomo Zodomo deleted the zodomo/avs-deregister-faq branch January 21, 2025 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants