docs: Update outdated Helm repository URL in README

Open Beginner friendly
#247 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
helm
Domain
documentation

Research direction

Open the README and find the Helm repository command using the outdated skylenet.github.io URL. Replace it with https://ethpandaops.github.io/ethereum-helm-charts, then verify that the documented command points to the active repository and no longer uses the unreachable URL.

Written by the indexing model from the issue text.

Description

Description

The README documentation for Checkpointz currently points to an outdated and unreachable Helm repository URL (https://skylenet.github.io/ethereum-helm-charts). This causes a 404 Not Found error when users attempt to add the repository.

The repository has been migrated to the official ethPandaOps GitHub Pages URL: https://ethpandaops.github.io/ethereum-helm-charts.

Steps to Reproduce
  1. Run the command listed in the README:
# Add the outdated ethereum-helm-charts repository
helm repo add ethereum-helm-charts https://skylenet.github.io/ethereum-helm-charts
  1. Actual Behavior
    The terminal returns the following error:
Error: looks like "https://skylenet.github.io/ethereum-helm-charts" is not a valid chart repository or cannot be reached: failed to fetch https://skylenet.github.io/ethereum-helm-charts/index.yaml : 404 Not Found
  1. Expected Behavior
    The documentation should be updated to point to the correct and active Helm repository URL:
# Add the correct ethereum-helm-charts repository
helm repo add ethereum-helm-charts https://ethpandaops.github.io/ethereum-helm-charts
Dominant language
Go
Stars
167
Forks
42
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from ethpandaops/checkpointz

All issues in ethpandaops/checkpointz

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.