add support for click and deploy release

.github/workflows/release-custom.yaml

@@ -0,0 +1,45 @@
+name: compspec-go custom tag and release
+
+on:
+  workflow_dispatch:
+    inputs:
+      release_tag:
+        description: Custom release tag
+        type: string
+        required: true
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+      - name: Set tag
+        run: |
+          echo "Tag for release is ${{ inputs.release_tag }}"
+          echo "tag=${{ inputs.release_tag }}" >> ${GITHUB_ENV}         
+      - uses: actions/checkout@v4
+      - name: Setup Go
+        uses: actions/setup-go@v3
+        with:
+          go-version: ^1.20
+
+      - name: Build
+        run: |
+          export PATH=$PWD/bin:$PATH
+          make 
+          make build-arm
+          make build-ppc
+
+      - name: Release
+        uses: softprops/action-gh-release@v1
+        with:
+          name: compspec-go ${{ env.tag }}
+          tag_name: ${{ env.tag }}
+          body: "compspec-go release ${{ env.tag }}"
+          files: |
+            bin/compsec
+            bin/compspec-arm
+            bin/compspec-ppc
+        env:
+          GITHUB_REPOSITORY: supercontainers/compspec-go

Makefile

@@ -1,13 +1,19 @@
 HERE ?= $(shell pwd)
 LOCALBIN ?= $(shell pwd)/bin
 
-.PHONY: all build
+.PHONY: all
 
-all: build-extract
+all: build
 
 .PHONY: $(LOCALBIN)
 $(LOCALBIN):
 	mkdir -p $(LOCALBIN)
 
-build-extract: $(LOCALBIN)
-	GO111MODULE="on" go build -o $(LOCALBIN)/compspec cmd/compspec/compspec.go
+build: $(LOCALBIN)
+	GO111MODULE="on" go build -o $(LOCALBIN)/compspec cmd/compspec/compspec.go
+
+build-arm: $(LOCALBIN)
+	GO111MODULE="on" GOARCH=arm64 go build -o $(LOCALBIN)/compspec-arm cmd/compspec/compspec.go
+
+build-ppc: $(LOCALBIN)
+	GO111MODULE="on" GOARCH=ppc64le go build -o $(LOCALBIN)/compspec-ppc cmd/compspec/compspec.go

docs/usage.md

@@ -132,6 +132,12 @@ a build will generate it for that context. We would want to save this to file:
 And that's it! We would next (likely during CI) push this compatibility artifact to a URI that is likely (TBA) linked to the image.
 For now we will manually remember the pairing, at least until the compatibility working group figures out the final design!
 
+## Check
+
+Check is the command you would use to check a potential host against one or more existing artifacts.
+For a small experiment of using create against a set of containers and then testing how to do a check, we are going to place content
+in [examples/check-lammps](examples/check-lammps).
+
 ## Extract
 
 Extraction has two use cases, and likely you won't be running this manually, but within the context of another command: