Proposal: allow pull requests for contributions to the pry GitHub wiki

[casaper]

I was just browsing the pry GitHub wiki for available plugins.

I noticed that there are some pry plugins that were not maintained for a long time
(e.g. on pry-exception_explorer – latest release was in 2012) outlined very prominently,
while others that I find useful (e.g. pry-doc) are not there.

I considered contributing a pull request, to propose some changes for that page.
Unfortunately, I soon realized that the GitHub wiki repo does not support pull requests.

The search engine I asked spit out this stack overflow question on that topic:

How can I make a pull request for a wiki page on GitHub?

There were multiple answers, but it seems the community there doesn't agree on a “best” solution.

What I could grasp as a possible solution:

• the stuff in the git@github.com/pry/pry.wiki.git repo is copied to a directory in the main repo – e.g. /pry/pry/tree/master/wiki
• someone like myself makes their pull request with changes to files in that wiki subdirectory
• there is a GitHub action that commits those changes to git@github.com/pry/pry.wiki.git on pull requests merge to master

This would have allowed me to contribute quickly.
You guys could have decided on whether you like my contribution or not, or if you demand changes to the contribution.
Just as ever, when you had some complete strangers like myself come up with code changes.

[casaper]

In case any of the maintainers of this repo here wants my brush up of the available plugins wiki page, they can also put the new markdown I made for it to the wiki for me, if they like it.

I basically converted it to modern markdown, and assorted and marked unmaintained gems into their own section.

Also added things like link to rubygems.org for each of the plugins.

Available-plugins.md