umeralifarooq

Projects Manager for GitHub allows you to showcase your GitHub portfolio on your WordPress site effortlessly. Simply enter a GitHub username, and the plugin will fetch all public repositories. You can then import specific repositories as “Projects” (Custom Post Types) to your site.
The plugin imports: 
* Repository Name & Description 
* Star, Fork, & Watcher Counts 
* Primary Language & Topics 
* Creation & Update Dates 
* Full README content (displays below the project details)
It integrates seamlessly with your active theme, ensuring your header, footer, and styles remain consistent.
<h4>Features</h4>
<ul>
<li>AJAX-based Fetching: Search for any GitHub user and fetch their repositories instantly without page reloads.</li>
<li>One-Click Import: Add repositories to your site with a single click.</li>
<li>Duplicate Prevention: Checks if a repository already exists to prevent duplicates.</li>
<li>Clean Integration: Uses WordPress’s standard <code>the_content</code> filter to append repository data, ensuring compatibility with almost all themes and page builders.</li>
<li>Security First: Built with strict sanitization, capability checks, and nonce verification.</li>
</ul>
<h3>External Services</h3>
This plugin connects to the GitHub API (api.github.com) to fetch public repository information. This is required for the core functionality of displaying GitHub repositories on your WordPress site.
What data is sent: 
* GitHub username (when searching for repositories) 
* Repository owner and name (when fetching README files)
When data is sent: 
* When you click “Fetch Repository” in the admin dashboard 
* When you import a repository to create a new project (to fetch README content)
Service provider: 
* GitHub, Inc. 
* Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service 
* Privacy Policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
Note: This plugin uses the public GitHub API which does not require authentication. No personal data from your WordPress site or your users is sent to GitHub.

Projects Manager for GitHub

Fetch public GitHub repositories via API and display them as native WordPress projects with your theme's header and footer.

Rob Landry

I was working on a plugin that had a pro (paid) version. This plugin had 2 code bases and was hosted on an external site. This site charged upwards of 50% of what I was charging.
So I became interested in finding a way to provide updates and use only one code base. I also wanted to minimize the cost to sell the plugin so that the money was not going into someone elses pocket. With Sell My Plugin, you host your own plugins. You use PayPal to charge for the purchases. There is a transactions list so that you can keep track of your sales. If you sell 10 copies of your plugin in a month at $10/ea, this plugin will save you $360 per year vs PlugPress and $600 vs CodeCanyon.
This plugin also uses the familiar domain.com/extend/plugins/ layout just like wordpress.
<h4>Free Features</h4>
<ul>
<li>Your.Domain.com/extend/plugins/ to list all of your plugins just like wordpress.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug to display the plugin info.</li>
<li>A custom search on the plugins page to search for available plugins.</li>
<li>Number of downloads tracked to see which plugins are HOT!!</li>
<li>News updates to provide you with up-to-date info on Sell My Plugin.</li>
<li>Shortcodes are provided to display the plugin where ever you want.</li>
<li>A <a href="http://redmine.landry.me/projects/sell-my-plugin/boards" rel="nofollow ugc">Forum</a> and <a href="http://redmine.landry.me/projects/sell-my-plugin/issues" rel="nofollow ugc">Bug Tracker</a> to get help.</li>
</ul>
<h4>Pro Features</h4>
<ul>
<li>If the plugin is a paid plugin, ?transaction= is added to:</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/version/ to allow downloads.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/update/ to display the update json to allow for plugin updates.</li>
<li>Your.Domain.com/extend/plugins/plugin-slug/update/ to display the update json to allow for plugin updates.</li>
<li>[sell-my-plugin] Displays the plugins list.</li>
<li>[sell-my-plugin slug=the-slug] Displays a small info box about the plugin.</li>
<li>[sell-my-plugin slug=the-slug format=full] Displays the full plugin info.</li>
<li>[sell-my-plugin slug=the-slug version=1.0 format=full] Displays the full plugin info for a particular version.</li>
<li>Transactions list for book keeping and tracking.</li>
<li>PayPal express checkout for purchase!</li>
<li>Downloads instantly activated upon completion of purchase.</li>
<li>UPDATES!! provided to plugins once a new version zip is uploaded!</li>
<li>PayPal Sandbox to test plugin purchases without mixing with REAL purchases.</li>
<li>Custom pricing of plugins in backend.</li>
<li>Ability to give paid plugins for free providing a FREE KEY!</li>
<li>
Custom email following purchase including shortcodes to allow for injection of PayPal data!
</li>
<li>
And many more!…
</li>
</ul>
<h3>Requirements</h3>
There are a few things that you need to do to make sure that you can use this plugin.
<h4>PHP 5 >= 5.2.0, PECL zip >= 1.5.0</h4>
This plugin makes use of the ZipArchive class, introduced in PHP 5.2.0. You must be running at least this version to use the plugin.
<h4>Valid readme.txt and plugin headers</h4>
Like plugins hosted on wordpress.org, you must include a valid readme.txt file and the proper plugin headers in your main plugin file. Check out a <a href="https://wordpress.org/extend/plugins/about/readme.txt" rel="ugc">sample readme.txt file</a> and use the <a href="https://wordpress.org/extend/plugins/about/validator/" rel="ugc">readme validator</a>. The Sell My Plugin plugin uses the readme.txt file and the plugin headers to render information about the plugin.

Sell My Plugin

It has zero downloads because it doesn't even work.



Doesn't Even Download

This plugin allows you to host your own plugins on your wordpress installation.

Projects Manager for GitHub vs Sell My Plugin