Currently this plugin allows only to get plugins from the CP Directory API.

Since the directory (or its owners) claim some sort of undocumented ownership over code, and requires too much manual work to maintain for a developer, and requires a forum account a developer might not want to partake in, at least TukuToi Plugins should be possible to be pulled directly from GitHub.

It should be relatively easy by listing to a new plugin header tag or similar.

• [x] Adds build process with gulp to generate .pot
• [x] Generates current string up for translation.

Run npm i && gulp watch to generate newly translated files. This would be a stepping block to help the move the project from English base only. There a number of string to make translatable as well in the project. This can be another PR to make it manageable to evaluate.

Thanks for the work on this.

I have two requests if you deem so would improve the product.

1. Increase the legibility by adjusting the contrast of the Report this plugin link to something darker. 20% seemed better for me.
2. Move the positioning adjacent to the contact the developer. This gives a visual hierarchy. I am also more likely to hit the report this plugin button when I want to install now or more details

While using the plugin, I felt like I had an unlimited options (This might be intended) I was overwhelmed not knowing where the end is. My request is to add number of available pages in pagination like in the screenshot. Thank you.

Currently the plugin pulls GitHub repos from TukuToi org, if the repo is tagged with classicpress-plugin Make it possible for an end user to add trusted Orgs/individuals in a simple to use setting, so to pull their repos as well, as long they are tagged appropriately

This feature should:

• provide a setting, perhaps with select2, to choose from orgs/individuals
• save that setting and show the choice
• then pull from those repos as well when enabled

It could be nice to offer the user the option to find orgs/ind without having to search for those, by simply APIing the tags of GitHub and pulling all orgs/ind from that, then offer them as a choice to the user (of course, with adequate "hey do you know what you do" warning)

[Added] AJAX loading the plugins list when empty or refreshing list. [Added] CRON daily event to check for new plugins/updates. [Added] Full integration with CP's new Directory API (plugins only). [Fixed] Missing (if available) GitHub Authentication when requesting readme.* files.

According report from Simone,

Seems that in admin/class-cp-plgn-drctry-github.php:275 should be

$readme = $this->get_remote_raw_body( 'https://raw.githubusercontent.com/' . $login . '/' . $item . '/' . $branch . '/' . $var, $this->set_auth() );

so you add authentication also when checking for readmes.

Currently when the plugin is first installed or a "refresh list" operation is done, a blocking remote get operation (which can take literal minutes) is performed.

This should be an AJAX operation with a spinner and perhaps some nice status updates/progress.

As this PR #7 shows, the plugin has an empty POT file. The workflow proposed in that PR is a bit too complicated since we can do everything as well with wp-cli, as Simone showed me.

I tried it and it works very well out of the box.

Thus, release 1.3 should include the POT file of strings.

Also PR #7 showed an issue with a string localised in /partials/display which needs to be fixed. This is going in the same.

When a user performs a number of searches, the URI gets longer and longer, resulting finally in a

The requested URL's length exceeds the capacity limit for this server.
Additionally, a 414 Request-URI Too Long error was encountered while trying to use an ErrorDocument to handle the request.

The fix should be to reset the search URL parameters when a user submits a new search. Found by Mark Davenport at CP.

[Added] Plugin Settings Page (under Admin > Settings > Manage CP Repos) [Added] Setting to add custom GitHub Repositories of Orgs, Users, and single repos [Added] Setting to store Personal GitHub Token, which increases the API Limits to 5k hourly instead of 60. [Added] Verified Orgs (not users) are pre-selected. A PR can be used to add new Orgs to the vetted list. [Added] Fundations to read remote readme, README, (both in md or txt) files. Currently used ony for below [Fixed] item. [Added] POT file for translators [Fixed] Untranslatable strings [Fixed] Problem where plugins with foldername/distinct-filename.php AND a unguessable Plugin Title could not be managed. [Improved] Make less calls to the GitHub API by re-using already queried data as much as possible. [Changed] Refactored code base