Skip to content
New issue

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

ci: adding test over selected plugins #13

Merged
merged 1 commit into from
Jul 13, 2024
Merged

ci: adding test over selected plugins #13

merged 1 commit into from
Jul 13, 2024

Conversation

teto
Copy link
Member

@teto teto commented Jul 11, 2024

No description provided.

@teto teto force-pushed the fix-workflow branch 5 times, most recently from 0a725f6 to 65807cc Compare July 11, 2024 22:33
... as expected by luarocks-tag-release

- doc: updated README
ci: adding test over selected plugins
@teto
Copy link
Member Author

teto commented Jul 11, 2024

rocky adventure but finally got something working,
I didn't want to require luarocks-tag-release changes to support list (along with string) for dependencies but this could make sense.

@teto teto requested a review from mrcjkb July 11, 2024 22:56
@teto teto merged commit d394520 into main Jul 13, 2024
1 check passed
@teto teto deleted the fix-workflow branch July 13, 2024 18:31
@teto
Copy link
Member Author

teto commented Jul 13, 2024

My changes seem to generate a correct rockspec, yet the luarocks install fail ?
https://github.com/nvim-neorocks/nurr/actions/runs/9922040583/job/27410665505#step:5:488

There seems to be unrelated failures as well such as neotest depending on the removed nvim-treesitter:
https://github.com/nvim-neorocks/nurr/actions/runs/9922040583/job/27410666847#step:5:545

for chatgpt.nvim
https://github.com/nvim-neorocks/nurr/actions/runs/9922040553/job/27410668231 gets

Error: /home/runner/work/nurr/nurr/chatgpt.nvim-0.1.1-alpha-1.rockspec: Type mismatch on field version: invalid value '0.1.1-alpha-1' does not match '[%w.]+-[%d]+' (using rockspec format 3.0)

The summary for the jobs are kinda confusing, I hope we can force the summary to just mention for which plugin it runs instead of some fields from the plugin such that sometimes a dependency appears first :s
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant