-
Notifications
You must be signed in to change notification settings - Fork 695
Open
Labels
Description
Describe the bug
Installing from brew, version 0.0.369, requires sudo. This wasn't happening before. I run an automated image creation, and this started to happen recently.
On the 2nd run, providing or not providing sudo access on the first time, it works normally, as if flags something to brew. To reproduce, I need to re-setup the from scratch, and then it happens at "all first times".
Affected version
0.0.369
Steps to reproduce the behavior
07:25 $ brew install copilot-cli
==> Downloading https://github.com/github/copilot-cli/releases/download/v0.0.369/copilot-linux-x64.tar.gz
==> Downloading from https://release-assets.githubusercontent.com/github-production-release-asset/585860664/91
####################################################################################################### 100.0%
==> Installing Cask copilot-cli
[sudo] password for lovato:
Sorry, try again.
[sudo] password for lovato:
sudo: 1 incorrect password attempt
lovato@f3677c698b41 ~
07:25 $ brew install copilot-cli
==> Downloading https://github.com/github/copilot-cli/releases/download/v0.0.369/copilot-linux-x64.tar.gz
Already downloaded: /home/lovato/.cache/Homebrew/downloads/fc523040e81b3e13c8f4df9e73b535c7e5ff5e634d346bbfa8250515db4310e3--copilot-linux-x64.tar.gz
==> Installing Cask copilot-cli
==> Linking Binary 'copilot' to '/home/linuxbrew/.linuxbrew/bin/copilot'
🍺 copilot-cli was successfully installed!
lovato@f3677c698b41 ~
07:29 $ copilot --version
0.0.369
Commit: 83653a1
Expected behavior
Install normally, w/o asking for any privileged access.
Additional context
No response