search

evalEmpire / gitpan

Git repositories for all of CPAN
http://github.com/gitpan
73 stars 12 forks source link

Use pull request templates to discourage pull requests on Gitpan repositories #132

Open oalders opened 8 years ago

oalders commented 8 years ago

This might be a good way to prevent pull requests: https://github.com/blog/2111-issue-and-pull-request-templates

schwern commented 8 years ago

It's a good idea. Unfortunately it's implemented by adding files to each repository. That would modify the data that we're archiving. :( Putting it into .github/ is a bit less odious, but still violates the basic idea of Gitpan as an archive.

ranguard commented 8 years ago

I would suggest that making it clear (even going so far as adding a README.md linking to metacpan for the module if one doesn't exist) would help save a lot of people's time.

An archive can have additional information added to it without it being compromised, as long as the additional information is documented as such.

book commented 8 years ago

On Fri, Jun 10, 2016 at 11:46:24AM -0700, Leo Lapworth wrote:

I would suggest that making it clear (even going so far as adding a README.md linking to metacpan for the module if one doesn't exist) would help save a lot of people's time.

An archive can have additional information added to it without it being compromised, as long as the additional information is documented as such.

Instead of adding the README.md to the files (I expect this could cause problems with distributions that ship a README.md?), what about putting the README alone on the master branch (so that everyone would see it when browsing github), with instructions about a cpan (gitpan?) branch which would contain the history, unchanged.

Philippe Bruhat (BooK)

As you search for youth, take care that it is not passing you by. (Moral from Groo The Wanderer #93 (Epic))