Compare commits

..

No commits in common. "main" and "v1.1.15" have entirely different histories.

2 changed files with 12 additions and 13 deletions

View File

@ -16,7 +16,7 @@ jobs:
- id: get-id - id: get-id
name: Get a unique tag for this build name: Get a unique tag for this build
run: | run: |
echo "DOCKER_IMAGE=${{ vars.GCP_DOCKER_REGISTRY }}/${{ github.repository }}:${{ inputs.image_tag }}" >> "$GITHUB_OUTPUT"; echo "DOCKER_IMAGE=${{ vars.docker_repo2_registry }}/${{ github.repository }}:${{ inputs.image_tag }}" >> "$GITHUB_OUTPUT";
- name: Print image name - name: Print image name
run: | run: |
@ -57,13 +57,13 @@ jobs:
- name: Push the container image - name: Push the container image
run: docker push ${{ steps.get-id.outputs.DOCKER_IMAGE }} run: docker push ${{ steps.get-id.outputs.DOCKER_IMAGE }}
# - name: Scan Docker Image for vulnerabilities with Grype - name: Scan Docker Image for vulnerabilities with Grype
# uses: anchore/scan-action@v6 uses: anchore/scan-action@v6
# with: with:
# image: ${{ steps.get-id.outputs.DOCKER_IMAGE }} image: ${{ steps.get-id.outputs.DOCKER_IMAGE }}
# cache-db: true #Cache Grype DB in Github Actions cache-db: true #Cache Grype DB in Github Actions
# output-format: table output-format: table
# only-fixed: true only-fixed: true
# severity-cutoff: critical severity-cutoff: critical
# fail-build: true fail-build: true

View File

@ -5,11 +5,10 @@ Github Action Workflows that can be reused, built by GMetri
## Creating new releases ## Creating new releases
```bash ```bash
commit_msg=v1.1.17
git add -A; git add -A;
git commit -m "$commit_msg" git commit -m "<commit msg>"
#Minor version #Minor version
git tag -a -m "$commit_msg" $commit_msg git tag -a -m "<tag msg>" v1.0.1
git push --follow-tags git push --follow-tags
#Moving major version #Moving major version
git tag -fa v1 git tag -fa v1