Consider pointing to releases page on Linux instead of tarball
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
While linking directly to a tarball is useful for users that use a directly extracted copy of VSCodium, for AppImage users being redirected to an archive when expecting a new AppImage is a confusing and frustrating experience.
Additionally, for users who use either Flatpak or their distribution's package manager, the experience is equally as confusing - potentially on these platforms could the update check either be disabled or the link replaced with a hint to update via their package manager?
Both of these potential issues could be resolved by linking directly to the Releases page, as every option of distribution is readily available, and the release notes could contain a reminder of how to update via a package manager.
I hope the reasoning behind this proposal makes sense, and I am eager to hear your opinions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the update service logic in this repository and reviewing how its version JSON files provide update links. Confirm whether the intended outcome is always linking to the VSCodium Releases page or handling AppImage, Flatpak, and package-manager users differently; done means the chosen behavior is implemented and verified for those distribution paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100