replicatedhq / replicatedhq/kURL

Off Topic: Thank you for krew.sh

Open
#5,679 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
809
Forks
81
Avg merge
1d 21h
Merged PRs (30d)
20

Description

I don't know where to put this, and I know it's not relevant to this repo. But found your site linked on krew.sh. Just wanted to say, thank you for creating it.

I spent 2 hours fighting with AI getting it to help me clean up the "litter" that is the "official" installation instructions for krew in my justfile recipe and automate adding its path to my profile so I can just install-krew in the future (because that time will come when I switch and re-roll my laptops). I just wanted to switch namespaces automatically. I am visually impaired and do programming basically night and day. Everything these days is 100x harder than it should be, and it takes me that much longer to find documentation and figure things out that someone could have just told me in one line in a README. Automating this stuff is becoming more and more necessary with all the complexity. And with AI to help maintainers improve their docs and roll automation scripts, there's really no excuse for any CLI installer to take more than one line.

Projects like Rust and Homebrew have been so easy to install with one line for years. So I asked the AI, why the heck is this so hard, why isn't there a one-liner, and it agreed with me and suggested there should be a curl krew.sh | bash, and I thought, nah, wouldn't that be nice? Gotta be a hallucination. So I looked, and voila. Unbelievable. Why isn't krew.sh listed in the official documentation? Seems like maybe a hard gatekeeper group to break into and get things like that, but maybe you can try to get them to help someone else at their wit's end and just link it. Thanks again!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is named. Review the user-facing installation documentation and determine whether it should link to krew.sh; done means the documentation change is agreed and the relevant link is added, if appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.