Make local repository higher priority than default #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
KSP-CKAN/NetKAN#9806 is failing validation because the validator is trying to install the old version of the module, without the PR's changes:
https://github.com/KSP-CKAN/NetKAN/actions/runs/6249249066/job/16965475746?pr=9806
https://github.com/KSP-CKAN/NetKAN/pull/9806/files
Cause
The validator adds the changes as a repo named
local
, and its priority ends up being 1, with the default repo remaining 0 priority. This means the default version of the module takes precedence.This worked previously because priority was not used and the sort was alphabetical, so
default
was overridden bylocal
.Changes
Now we set the priority of the
local
repo to 0, so the PR's changes will override the default repo.I'll self-review this so I can see if it helps that PR.