p5-Dist-Zilla-Plugin-GitHub

p5-Dist-Zilla-Plugin-GitHub copied to clipboard

yanick

Instead of using `origin` try to fetch it from git first using for example result of ``` git branch -rl "*/HEAD" ``` or (expecting `master` to be default branch) ```...

happy-barney

This is to address #50. I realize it is a bit strict. But I think it makes sense when releasing to be strict about information being available.

horgh

Fail if GitHub API request returns 404

1

This is as discussed in #56. Note it changes the default behaviour to fail if we get a 404 when making API requests. Personally I don't know why you'd want...

horgh

Recognise GitHub remotes without .git suffix

1

This is related to discussion in #56.

horgh

Use token authentication

1

I noticed it said in the log that token auth was deprecated. That may be true for using the token as a password, but token authentication is alive and well....

Altreus

HTTP authentication method will expire soon

3

I created a new local distribution and received the following email from github: ``` You recently used a password to access an endpoint through the GitHub API using HTTP-Tiny/0.056_001. We...

sdondley

Check for required information prior to release step

3

I use these plugins as part of a bundle, and I found at least `GitHub::Update` checks for some information it needs only after the release, and then errors if it...

horgh

"Getting GitHub repository info" fails with "Err: Not Found"

6

This was with version 0.46 as well. The same release as in #55. In the build step I see this: ``` [@MAXMIND/GitHub::Meta] Getting GitHub repository info [@MAXMIND/GitHub::Meta] Err: Not Found...

horgh

Just a little reminder for myself. It'd be nice to have a plugin that creates a new GitHub release on `dzil release`. See [the API docs](https://developer.github.com/v3/repos/releases/#create-a-release).

ghedo