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

Tweak wording for the "Manual download" info on the download page #278

Merged
merged 4 commits into from
Jul 24, 2024

Conversation

DeeDeeG
Copy link
Member

@DeeDeeG DeeDeeG commented Jul 18, 2024

I thought this text could use a bit of an update. See diff for details.

docs/download.md Outdated
Comment on lines 215 to 216
Apple silicon and ARM Linux binaries are usually grouped together
in their own separate release from the x64 binaries, but sometimes not.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Apple silicon and ARM Linux binaries are usually grouped together
in their own separate release from the x64 binaries, but sometimes not.
Apple silicon and ARM Linux binaries are usually, but not always, grouped together
in their own separate release.

@Daeraxa
Copy link
Member

Daeraxa commented Jul 19, 2024

I remember that conversation about "being logged in" etc. but didn't think we had pushed it to the site in that way. Thanks for noticing it and tidying it up.

docs/download.md Outdated
@@ -190,28 +190,32 @@ You can bypass this by clicking "More info" then "Run anyway".
## Manual download

Binaries are built from a number of different branches and PRs but you should
stick to the **master** branch releases for the most stable ones unless you know
stick to the **`master`** branch releases for the most stable ones unless you know
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
stick to the **`master`** branch releases for the most stable ones unless you know
stick to the `master` branch releases for the most stable ones unless you know

I'd probably remove the strong from this as I think converting it to inline code is enough to differentiate it.

@confused-Techie
Copy link
Member

If we update this PR from main with the changes I just made in #279 we can get the Test Deployment passing

Copy link
Member

@confused-Techie confused-Techie left a comment

Choose a reason for hiding this comment

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

This looks great to me!

@DeeDeeG
Copy link
Member Author

DeeDeeG commented Jul 24, 2024

Alright, thanks for the review!

And somehow CI passed here, so perhaps the outdated pnpm action failure is not 100% but rather something like 70-90%? We've updated it now, though, so should be no issue going forward...

Anyhow, merging!

@DeeDeeG DeeDeeG merged commit 10c1602 into main Jul 24, 2024
2 checks passed
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.

3 participants