-
Notifications
You must be signed in to change notification settings - Fork 4
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
Octopolo asks label-related questions as an array of objects #123
Conversation
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.
Seems like a solid refactor. QA works fine. Just the one question...
lib/octopolo/cli.rb
Outdated
@@ -114,21 +114,18 @@ def self.perform_in(dir) | |||
|
|||
def self.ask(question, choices, skip_asking = false) | |||
return choices.first if choices.size == 1 | |||
|
|||
unless skip_asking |
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.
Why ignore this param now?
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.
If I'm understanding the code correctly, we never actually call this method with the skip_asking
set to true
, unless it's in a test. So I'm not sure if there was a point keeping it around. Seemed to just confuse me. I could put it back in, but by the time I realized we could keep it, I had already moved around the tests.
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.
Can we take it out of the method signature then (on line 115)? I'm sure Rubocop wouldn't like us leaving it around...
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.
Oh right. missed that
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.
Approved!
|
What and Why
No user-facing changes. Update how octopolo asks the user to update labels: although it will look the same to users right now, actually have asking a label-related question make a octopolo question object, and then ask each object. This creates the ability to ask the users multiple label-related questions for each PR or issue, instead of just a hard-coded single question.
Deploy Plan
Merge this PR and make a new release (minor version change). Put new release on RubyGems.
Rollback Plan
To roll back this change, revert the merge with
git revert -m 1 MERGE_SHA
and perform another deploy.QA Plan
bundle install
(rungem install bundler
before this command if necessary)bin/op pull-request
to make a test PR using this codebin/op issue
to make a test issue using this code