1. Obtain a github account if you don't already have one.
  2. Fork the repo
  3. Make changes to your fork
  4. Raise the pull request

OK...

I already had a github account and have forked the repo, made the changes...

What's the right way to test it?
I've installed git but I've not used that for the PR. I've done it all online. The only file that needed changing was /Module/Starter/Somple.pm

I could just make the same change in my local copy installed from CPAN and test that. Although that would work for this simple change, it doesn't seem a good or scalable method of testing changes.

In reply to Re^2: GitHub PR (was: Re^4: CPAN Ratings...) by Bod
in thread CPAN Ratings... by Bod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.