Windows CLI Build

After extracting the Windows CLI tool from here:

I extracted it and found it was just “drone”. Running “drone” with that as is wouldn’t work, until I renamed it “drone.exe”, after which it launched.

Shouldn’t the Windows tool automatically be named “drone.exe” inside the tarball instead of just “drone”?

I do not have much windows experience, so I would defer to those running windows. If a .exe extension is required, the build script would need to be updated accordingly.

# compile for all architectures
GOOS=linux   GOARCH=amd64 go build -ldflags "-X main.version=${DRONE_TAG##v}" -o release/linux/amd64/drone
GOOS=linux   GOARCH=arm64 go build -ldflags "-X main.version=${DRONE_TAG##v}" -o release/linux/arm64/drone
GOOS=linux   GOARCH=arm   go build -ldflags "-X main.version=${DRONE_TAG##v}" -o release/linux/arm/drone
-GOOS=windows GOARCH=amd64 go build -ldflags "-X main.version=${DRONE_TAG##v}" -o release/windows/amd64/drone
+GOOS=windows GOARCH=amd64 go build -ldflags "-X main.version=${DRONE_TAG##v}" -o release/windows/amd64/drone.exe
GOOS=darwin  GOARCH=amd64 go build -ldflags "-X main.version=${DRONE_TAG##v}" -o release/darwin/amd64/drone

# tar binary files prior to upload
tar -cvzf release/drone_linux_amd64.tar.gz   -C release/linux/amd64   drone
tar -cvzf release/drone_linux_arm64.tar.gz   -C release/linux/arm64   drone
tar -cvzf release/drone_linux_arm.tar.gz     -C release/linux/arm     drone
-tar -cvzf release/drone_windows_amd64.tar.gz -C release/windows/amd64 drone
+tar -cvzf release/drone_windows_amd64.tar.gz -C release/windows/amd64 drone.exe

Yeah, that change looks perfect to me.