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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature wish: Add a --yes flag to automatically accept Confirm questions #132

Closed
erikmd opened this issue Oct 5, 2021 · 2 comments 路 Fixed by #158
Closed

Feature wish: Add a --yes flag to automatically accept Confirm questions #132

erikmd opened this issue Oct 5, 2021 · 2 comments 路 Fixed by #158

Comments

@erikmd
Copy link

erikmd commented Oct 5, 2021

In order to be able to use opam publish in "batch mode", directly from a GH Action, I believe it would be very handy to have a -y or so flag, a bit like opam 馃檪

Note: I tried yes | opam publish --no-browser --msg-file=CHANGES.md --tag $tag_name $user/$repo but got:

You will be shown the patch before submitting.
Please confirm the above data. Continue ?  [Y/n] n
yes: standard output: Broken pipe
Error: Process completed with exit code 10.
erikmd added a commit to pfitaxel/learn-ocaml that referenced this issue Oct 5, 2021
* Use var OPAM_RELEASE (GitHub PAC)

* Use "expect" to workaround the lack of this feature:
  ocaml-opam/opam-publish#132

Co-Authored-By: Yann R茅gis-Gianas <yann@regis-gianas.org>
Co-Authored-By: Erik Martin-Dorel <erik@martin-dorel.org>
erikmd added a commit to pfitaxel/learn-ocaml that referenced this issue Oct 5, 2021
* Use var OPAM_RELEASE (GitHub PAC)

* Use "expect" to workaround the lack of this feature:
  ocaml-opam/opam-publish#132

Co-Authored-By: Yann R茅gis-Gianas <yann@regis-gianas.org>
Co-Authored-By: Erik Martin-Dorel <erik@martin-dorel.org>
erikmd added a commit to ocaml-sf/learn-ocaml that referenced this issue Oct 5, 2021
* Use var `OPAM_RELEASE` (GitHub PAC)

* Use `expect` to workaround the fact that the feature wish
  ocaml-opam/opam-publish#132
  is not yet available.

Co-Authored-By: Yann R茅gis-Gianas <yann@regis-gianas.org>
Co-Authored-By: Erik Martin-Dorel <erik@martin-dorel.org>
@phated
Copy link
Contributor

phated commented Nov 8, 2021

It seems that v2.1.0 of opam-publish doesn't respect OPAMYES=1 for some reason. I can't quite understand why.

@phated
Copy link
Contributor

phated commented Nov 8, 2021

I downgraded to opam-publish v2.0.3 in my local env and it works again.

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

Successfully merging a pull request may close this issue.

2 participants