Optional github integration (--[no-]github support) #186
Conversation
|
Very nice. There's been a long standing request open for support for not using git/github, and this definitely is a step towards that. I'll review & merge this soon (hopefully). One thing to consider would be how to document this in a way that folks can find it. If you can think of anything, by all means let me know! |
|
Readme file? Do you have release blog in jeweler? Changing the current behavior to disable github support by default would be dramatic step but considerable for a further major release. |
|
Had a chance to look at this more closely, and it's actually reallllly close to being everything needed for non-git support. I've left some in line comments on the commits. The only major consideration I can think of would be the impact of not having a git repository around when using the rake tasks. I'm not positive if they assume it's there or not, but it should be straightforward to only conditionally do some things. |
|
I'm closing out old PRs as part of #283 . I'm sorry I was never able to help get this to a point to be merged. |
This patch allows the user to create a jeweler project structure without having any git(+hub) integration. I've added the option in a way the tool still behaves in the original way and tries to add fully github support, so it should provide full backward compatibility.
To disable github support the user just has to apply the --no-github option.