We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I am trying to add support to Mason (Vim LSP manager) in order to fix japhib/pico8-ls#34
Mason uses bot called renovate to detect new releases of a package.
If the releases used github tags (or github releases), Mason should be able to track new releases from there.
Without them, the best we can do is use is the git-refs datasource. This will track the HEAD of the repository.
The release process for this repo would have to be changed to push a new git tag when a new release is done. Something like:
git tag -a 0.6.0 -m 0.6.0 git push origin 0.6.0
Alternatively a new github release could be done. This might be more involved - the gh command-line tool might help there.
gh
No response
The text was updated successfully, but these errors were encountered:
Woops. Wrong repo. Closing, apologies
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
Hi, I am trying to add support to Mason (Vim LSP manager) in order to fix japhib/pico8-ls#34
Mason uses bot called renovate to detect new releases of a package.
If the releases used github tags (or github releases), Mason should be able to track new releases from there.
Without them, the best we can do is use is the git-refs datasource. This will track the HEAD of the repository.
Describe the solution you'd like
The release process for this repo would have to be changed to push a new git tag when a new release is done. Something like:
Describe potential alternatives you've considered
Alternatively a new github release could be done. This might be more involved - the
gh
command-line tool might help there.Additional context
No response
The text was updated successfully, but these errors were encountered: