Skip to content

feat(gh_actions_ls): allow .forgejo and .gitea as root_dir #3566

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

Merged
merged 3 commits into from
Jan 21, 2025

Conversation

Crashdummyy
Copy link
Contributor

The projects forgejo and gitea share the same syntax even across the composite actions.
There are only negligible differences IMHO which besides the actions author should be aware of.
Besides its only a matter of time until those become implemented as well.

It'd be a nice addition to let it attach for those systems as well

@justinmk
Copy link
Member

seems fine but should be called out in the docs

Copy link
Contributor

Note that configs.md or configs.txt will be regenerated by the docgen CI process. Edit the Lua source file instead. For details on generating documentation, see: https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#generating-docs

1 similar comment
Copy link
Contributor

Note that configs.md or configs.txt will be regenerated by the docgen CI process. Edit the Lua source file instead. For details on generating documentation, see: https://github.com/neovim/nvim-lspconfig/blob/master/CONTRIBUTING.md#generating-docs

@justinmk justinmk merged commit 71eac2a into neovim:master Jan 21, 2025
11 checks passed
@justinmk justinmk changed the title refactor(gh_actions_ls): allow .forgejo and .gitea as root_dir feat(gh_actions_ls): allow .forgejo and .gitea as root_dir Jan 21, 2025
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.

2 participants