-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make slackistrano optional #7
base: master
Are you sure you want to change the base?
Conversation
capistrano-antistatique.gemspec
Outdated
@@ -24,7 +24,6 @@ Gem::Specification.new do |spec| | |||
|
|||
spec.add_dependency 'capistrano', '~> 3.5' | |||
spec.add_dependency 'capistrano-composer', '~> 0.0.6' | |||
spec.add_dependency 'slackistrano', '~> 3.1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose this break BC but slackistrano should be optional
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could keep the gem dependency as that doesn't have so much effect. But if you want to remove it, why not.
require 'capistrano/antistatique/httpauth' | ||
require 'capistrano/antistatique/slackistrano' | ||
require 'capistrano/antistatique/styleguide' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this file should be removed because even styleguide is optional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. But this will be a BC break, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's a breaking change if you update the module on a project, but also an easy fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And that will probably not break the build, just stop to send notifications. Also, the dependency was removed from gemspec, so makes no sense to have this here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, the Gemfile.lock
works as expected (https://github.com/antistatique/cardis-server/blob/dev/Gemfile.lock#L2-L3)
Is the [0.1.0](https://github.com/antistatique/cardis-server/blob/dev/Gemfile#L7)
doing something useful in the case of a reference to a git ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's useless
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only case that must be specified if not gem spec exist in the repository if I remember correctly
capistrano-antistatique.gemspec
Outdated
@@ -24,7 +24,6 @@ Gem::Specification.new do |spec| | |||
|
|||
spec.add_dependency 'capistrano', '~> 3.5' | |||
spec.add_dependency 'capistrano-composer', '~> 0.0.6' | |||
spec.add_dependency 'slackistrano', '~> 3.1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could keep the gem dependency as that doesn't have so much effect. But if you want to remove it, why not.
@gido About that, i think we should remove everything from Do you agree with that? |
Yes. I'm in favor to cherry-pick for each project which recipes we need. |
This reverts commit ba7f81a.
💬 Describe the pull request
What if I don't want slackistrano ?