Add plugin marketplace (for official plugins)

[anbraten]

closes #315

List of Plugins is fetched on each build of the documentation.
Plugins are search by this query string:

// search for repos in woodpecker-ci org with the topic: woodpecker-plugin including forks

org:woodpecker-ci topic:woodpecker-plugin fork:true

https://github.com/search?q=org%3Awoodpecker-ci+filename%3Adocs.md+WOODPECKER_PLUGIN_DOCS

You can find a sample documentation for a plugin here: https://github.com/woodpecker-ci/plugin-demo/blob/main/docs.md

Preview

https://extra-small-jelly.surge.sh/plugins

[anbraten]

Okay lets move that discussion about third-party plugins from this PR to an issue: #453. I think or at least I hope so 😉, we all like the idea of having some list of at least the official plugins (git, docker, cache, ...) for now. We can start with opening the list then from time to time. So please add your ideas to #453 so we can discuss there and only add feedback regarding the "technical" index / list feature in here. THX

[anbraten]

I changed the code to search for all repositories with the following query: org:woodpecker-ci topic:woodpecker-plugin fork:true now.

[jolheiser]

I changed the code to search for all repositories with the following query: org:woodpecker-ci topic:woodpecker-plugin fork:true now.

Do we need the fork:true part? The topic should work well enough and we may have non-forked plugins eventually, right?

Other than that I think this is close. 🙂

[6543]

We will have fork and non-forked plugin repos ...

[anbraten]

We need fork: true it only means include forks (not search only for forks). Tested it with plugin-demo (no fork) and plugin-s3, plugin-git (both forks from drone plugins) and seems to work correctly.

[jolheiser]

We need fork: true it only means include forks (not search only for forks). Tested it with plugin-demo (no fork) and plugin-s3, plugin-git (both forks from drone plugins) and seems to work correctly.

Ah, my bad. Seems like an ambiguous query on GHs part.
https://docs.github.com/en/search-github/searching-on-github/searching-in-forks
fork:true includes forks (like you've done)
fork:only is for only forks 🤦

[anbraten]

Yeah this option naming by Github is not the best.

[jolheiser]

My only remaining nits are

1. Remove the issue template
2. For now it's probably fine, but we may want to think about how to deal with docs from third-party plugins. I don't know that throwing them onto the page is a best idea unless we can properly santize them.
3. Is there any way we can cache results? Hitting the GH API for each person who views the page seems like we might hit a ratelimit.

[6543]

@jolheiser @anbraten
a. I did add logging back - it was usefully while looking at this pull ...

b. if i understand it right, we only hit github once per doc-build, so that should be ok?

[jolheiser]

b. if i understand it right, we only hit github once per doc-build, so that should be ok?

Oh interesting, maybe I missed that part. I thought this was running on the page. If it's just to build static content that should be fine.

EDIT:

List of Plugins is fetched on each build of the documentation.

I can't read. 🤦

---

For the issue template, I was under the impression this PR was for "official" plugins, as in we own them in our org.

Community plugins may need a bit more strategy.