Skip to content

fix(docs): update installation instructions to extract binary from tarball - #496

Merged
VelmiraS merged 1 commit into
masterfrom
fix/installation-docs-tarball
Sep 11, 2026
Merged

VelmiraS merged 1 commit into
masterfrom
fix/installation-docs-tarball

Conversation

@VelmiraS

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:
Release artifacts published to GitHub are gzip tarballs, not plain executables. The previous installation instructions only ran chmod +x on the downloaded file, which caused an exec format error when users tried to run it. This PR updates the README to include the tar -xzf extraction step.

Which issue(s) this PR fixes:
Fixes #495

Special notes for your reviewer:

Release note:

Installation instructions in the README now correctly include extracting the binary from the downloaded tarball before running it.

@gardener-prow gardener-prow Bot added do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 11, 2026

@klocke-io klocke-io left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🚀

Nice, if you want to, you could also add a simple script that checks the operating system and architecture, downloads the correct and latest release and unzips it. Since most people probably would be using docforge in some for of CI pipline.

gardener-documentation, has something you could use as inspiration :)

@gardener-prow gardener-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2026
@gardener-prow

gardener-prow Bot commented Sep 11, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: klocke-io

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow

gardener-prow Bot commented Sep 11, 2026

Copy link
Copy Markdown

LGTM label has been added.

DetailsGit tree hash: 3815e1154a3e44adcb90f6a96ba8528626d60afa

@gardener-prow gardener-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 11, 2026
@VelmiraS
VelmiraS merged commit 2bb114d into master Sep 11, 2026
52 of 55 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation of binary download is incorrect

2 participants