Paul Clark

I may have not written clearly. I'm saying Git updates from `Plugin URI` off by default. The consequence being that any plugin with a Git address in `Plugin URI` would...

`PluginURI` has been disabled for Git updates in https://github.com/brainstormmedia/git-plugin-updates/commit/20fb1ac2228b484b7b59f35e684a5c2410ce6cc7

Is this now a duplicate of #20, or is there another component I'm missing?

I'm pretty backlogged right now, so I might not have a chance to debug this for a while (and even then, it would be helpful to have some sort of...

Is there an advantage to doing it this way when all the info can be detected by copying-and-pasting the repo URL? I assume you're talking about a format like this?...

This is still confusing to me. Maybe we could chat on Skype? If the purpose is to provide two ways to configure the updater, it seems redundant. If the purpose...

Or put another way, what is the problem this solves? ``` /* Plugin URI: http://wordpress.org/someplugin Git URI: http://github.com/owner/someplugin */ /* Plugin URI: http://wordpress.org/someplugin Git(hub) URI: owner/someplugin */ ``` These both...

`Plugin URI` should be fixed (disabled) in this commit: https://github.com/brainstormmedia/git-plugin-updates/commit/20fb1ac2228b484b7b59f35e684a5c2410ce6cc7 Can you tell me a bit more about supporting `owner/repo` in the `Git URI` field? Is it just for shorthand?

(Or, just link me to @GaryJones's original feature request.)

If you want to submit a pull request to allow that with the legacy headers, I'll accept it. As long as we don't document it as an option. It'd also...