Skip to content
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

Feedback on trying to adopt cherry-picker within @ansible/ansible #263

Closed
webknjaz opened this issue Jun 14, 2018 · 2 comments
Closed

Feedback on trying to adopt cherry-picker within @ansible/ansible #263

webknjaz opened this issue Jun 14, 2018 · 2 comments

Comments

@webknjaz
Copy link
Contributor

Hi @Mariatta,

So as other people started trying out cherry_picker-based flow, some failures to use it happened:

  • It seems like there's not enough terminal output to completely understand when something goes wrong
  • Failed branches disappear without explanation
  • It looks like it pushes into wrong branch, but there's not enough verbosity to verify this.

Ref: ansible/ansible#41403
cc: @abadger

@Mariatta
Copy link
Member

I think all of these have been resolved in the 1.2.1 release, right?

@webknjaz
Copy link
Contributor Author

Yes, #277 will be addressed separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants