-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
Some repos only take PRs, but not issues.
I get asked periodically why I create issues and not PRs. So, here's an issue describing some of the technical concerns.
To do this, there's a number of things to consider, though there may be some mvp.
- Is there a license file (accommodate spelling variants), and if so which license is it (match against known licenses)
- Scrape the README for possible licenses
- Figure out which file to change, the gemspec, the Rakefile, a custom gem task?
- Determine if that change has already been made, but is unreleased
- Handle multiple licenses
- Tweaking the changes in the PR would now be dependent on my branch
- I would end of forking quite a few repos!
Ironically, if there were a script good enough at guessing the license for a project, rubygems.org might not need to rely on the gemspec. 😄
Other concerns would be
- to make the PR attractive
- to ensure it is inline with Github ToS
Metadata
Metadata
Assignees
Labels
No labels