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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi 馃憢
When navigating to https://go-vela.github.io/docs/plugins/, I expected to see a list of plugins available as a Vela user. I was able to get a list by going back to GitHub and searching for plugins under this organization (full list is: https://github.com/go-vela?q=plugin&type=all&language=&sort=)
Is there a way to generate a list on that page? Is the user expectation to navigate to each repo to learn how to use the individual plugins?
I'd love to clarify the user expectations of this workflow. Thanks!
The text was updated successfully, but these errors were encountered:
thanks for the the feedback, for a one-pager, this is probably as close as we have one right now: https://go-vela.github.io/docs/plugins/registry/pipeline/. all the plugin repos are tagged with a topic though: https://github.com/topics/vela-plugin.
is the expectation to head to each repo for usage? currently, yes. in fact, all we are doing on our docs pages is pull in each repo's usage docs, https://raw.githubusercontent.com/go-vela/docs/main/content/plugins/registry/pipeline/ansible.md for example.
can this be better? most definitely. in many ways. if you have some ideas, we're happy to check them out.
Sorry, something went wrong.
transferring to community issues
No branches or pull requests
Hi 馃憢
When navigating to https://go-vela.github.io/docs/plugins/, I expected to see a list of plugins available as a Vela user. I was able to get a list by going back to GitHub and searching for plugins under this organization (full list is: https://github.com/go-vela?q=plugin&type=all&language=&sort=)
Is there a way to generate a list on that page? Is the user expectation to navigate to each repo to learn how to use the individual plugins?
I'd love to clarify the user expectations of this workflow. Thanks!
The text was updated successfully, but these errors were encountered: