Dist-Zilla-Plugin-GitHub-CreateRelease

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

     login github_username OR github_organization
     token github_....

    The GitHub API has a lot of options for the generation of Personal
    Access Tokens.

    At minimum you will need a personal access token with "Write" access to
    "Contents". It allows write access to Repository contents, commits,
    branches, downloads, releases, and merges.

    Config::Identity::GitHub supports a gpg encrypted .github-identity file.
    It is recommended that you implement encryption for the .github-identity
    file. If you have gpg configured you can encrypt the file:

     # Encrypt it to ~/.github-identity.asc
     gpg -ea -r you@example.com ~/.github-identity
     # Cat ~/.github-identity.asc to verify it is encrypted
     cat ~/.github-identity.asc
     # Verify you can decrypt the file
     gpg -d ~/.github-identity.asc
     # Replace the clear text version (uncomment next line)
     # mv ~/.github-identity.asc ~/.github-identity

  PERSONAL ACCOUNT VERSUS ORGANIZATION
    The login specified in the .github-identity file above should reference
    the personal account OR the organization that contains the repo.

    A personal access token must have the Resource owner set to the
    organization but does not require special permissions on the
    organization. It simply needs read/write on the code and read access on

dist.ini  view on Meta::CPAN

web = https://github.com/timlegge/perl-Dist-Zilla-Plugin-GitHub-CreateRelease/issues
[MetaResources]
homepage   = https://metacpan.org/dist/Dist-Zilla-Plugin-GitHub-CreateRelease

[Test::PodSpelling]
stopword = AfterBuild
stopword = plaintext
stopword = FromFile
stopword = SignReleaseNotes
stopword = api
stopword = gpg
stopword = webpage

[PodSyntaxTests]
[PodCoverageTests]
[Test::Perl::Critic]
[Test::EOL]
[Test::EOF]
[Test::NoTabs]
[Test::TrailingSpace ]

lib/Dist/Zilla/Plugin/GitHub/CreateRelease.pm  view on Meta::CPAN

 login github_username OR github_organization
 token github_....

The GitHub API has a lot of options for the generation of Personal Access Tokens.

At minimum you will need a personal access token with "Write" access to "Contents".
It allows write access to Repository contents, commits, branches, downloads,
releases, and merges.

Config::Identity::GitHub supports a gpg encrypted B<.github-identity> file.  It is
recommended that you implement encryption for the B<.github-identity> file.  If you
have gpg configured you can encrypt the file:

 # Encrypt it to ~/.github-identity.asc
 gpg -ea -r you@example.com ~/.github-identity
 # Cat ~/.github-identity.asc to verify it is encrypted
 cat ~/.github-identity.asc
 # Verify you can decrypt the file
 gpg -d ~/.github-identity.asc
 # Replace the clear text version (uncomment next line)
 # mv ~/.github-identity.asc ~/.github-identity

=head2 PERSONAL ACCOUNT VERSUS ORGANIZATION

The B<login> specified in the B<.github-identity> file above should reference the
personal account B<OR> the organization that contains the repo.

A personal access token must have the B<Resource owner> set to the organization but
does not require special permissions on the organization.  It simply needs read/write

t/author-pod-spell.t  view on Meta::CPAN

FromFile
GitHub
Legge
Plugin
SignReleaseNotes
Timothy
Zilla
api
bin
createrelease
gpg
lib
plaintext
webpage