Use package control version resolution method for tags
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start at the actions/setup entry point and compare its current tag resolution with the Package Control manifest resolution strategy linked in the issue. Check how the installed Sublime Text version is available to the action, then verify that matching tags are selected automatically while an explicit package tag still overrides the choice.
Written by the indexing model from the issue text.
Description
I've specified MarkdownEditing:SublimeText-Markdown/MarkdownEditing as an extra-packages in actions/setup and was surprised to see that an ancient 2.2.10 version was installed
Reading the comments more carefully, the action ignores the package control resolution strategy: https://github.com/sublimehq/package_control_channel/blob/b8b340ab5398a7651f6770b656bccd5dda258c09/repository/m.json#L671-L672 , and defaults to basic untagged semver o
If an exact match is not found, the latest tag is determined by semver x.y.z
or forces users to pick a tag (which could break once ST version are updated)
@refbranch/tag name or prefix of tags e.g.st3-or empty
Could the action instead of forcing an explicit specification of a prefix use the Package Control manifest to pick the one that fits the installed Sublime Text version? And then CI users would only need to specify a given package tag to override
- Dominant language
- Python
- Stars
- 113
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
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.
More from SublimeText/UnitTesting
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SublimeText/UnitTesting#276 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
SublimeText/UnitTesting#209 · 8 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SublimeText/UnitTesting#155 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
SublimeText/UnitTesting#31 · 5 comments ·
All issues in SublimeText/UnitTesting
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·