feat: detect actual upstream #5

Merged
nin0 merged 8 commits from Benjas333/userpluginInstaller:feat/detect-actual-remote into main 2026-04-24 16:42:36 -04:00
Contributor

If this PR does not meet the project goals/criteria, I get it.

Context

I tend to fork multiple userplugins because of maintenance, among other reasons, and it's a little (bit) annoying that userplugins says there's an update available because it's hard-coded to fetch origin/HEAD. So, this PR fixes that by detecting the actual upstream of the current branch.

Changelog

Added

  • getUpstream() async function (falls back to origin/HEAD)
  • awaitableExec wrapper function (in case you want to reuse it)

Changed

  • isUpdateAvailableForPlugin and updatePlugin now use getUpstream()
If this PR does not meet the project goals/criteria, I get it. ## Context I tend to fork multiple userplugins because of maintenance, among other reasons, and it's a little (bit) annoying that userplugins says there's an update available because it's hard-coded to fetch origin/HEAD. So, this PR fixes that by detecting the actual upstream of the current branch. ## Changelog ### Added - `getUpstream()` async function (falls back to origin/HEAD) - `awaitableExec` wrapper function (in case you want to reuse it) ### Changed - `isUpdateAvailableForPlugin` and `updatePlugin` now use `getUpstream()`
Benjas333 changed title from feat: detect actual upstream to WIP: feat: detect actual upstream 2026-04-24 11:15:05 -04:00
Author
Contributor

I've realized I made the isUpdateAvailableForPlugin() fall back wrong. Will fix it when I'm at my computer.

I've realized I made the `isUpdateAvailableForPlugin()` fall back wrong. Will fix it when I'm at my computer.
Benjas333 changed title from WIP: feat: detect actual upstream to feat: detect actual upstream 2026-04-24 14:23:00 -04:00
nin0 merged commit 4c7066708a into main 2026-04-24 16:42:36 -04:00
nin0 deleted branch feat/detect-actual-remote 2026-04-24 16:42:36 -04:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
userplugins/userpluginInstaller!5
No description provided.