There's no point on running lint over the prepare release changes

Signed-off-by: Pedro Algarvio <palgarvio@vmware.com>

.github/workflows/ci.yml

@@ -300,6 +300,8 @@ jobs:
 
       - name: Commit Changes
         shell: bash
+        env:
+          SKIP: lint-salt,lint-tests
         run: |
           # Run it twice so that pre-commit can fix anything that can be automatically fixed.
           git commit -am "Release v${{ needs.prepare-workflow.outputs.salt-version }}" || \

.github/workflows/nightly.yml

@@ -298,6 +298,8 @@ jobs:
 
       - name: Commit Changes
         shell: bash
+        env:
+          SKIP: lint-salt,lint-tests
         run: |
           # Run it twice so that pre-commit can fix anything that can be automatically fixed.
           git commit -am "Release v${{ needs.prepare-workflow.outputs.salt-version }}" || \

.github/workflows/scheduled.yml

@@ -298,6 +298,8 @@ jobs:
 
       - name: Commit Changes
         shell: bash
+        env:
+          SKIP: lint-salt,lint-tests
         run: |
           # Run it twice so that pre-commit can fix anything that can be automatically fixed.
           git commit -am "Release v${{ needs.prepare-workflow.outputs.salt-version }}" || \

.github/workflows/staging.yml

@@ -331,6 +331,8 @@ jobs:
 
       - name: Commit Changes
         shell: bash
+        env:
+          SKIP: lint-salt,lint-tests
         run: |
           # Run it twice so that pre-commit can fix anything that can be automatically fixed.
           git commit -am "Release v${{ needs.prepare-workflow.outputs.salt-version }}" || \

.github/workflows/templates/ci.yml.jinja

@@ -149,6 +149,8 @@ on:
 
       - name: Commit Changes
         shell: bash
+        env:
+          SKIP: lint-salt,lint-tests
         run: |
           # Run it twice so that pre-commit can fix anything that can be automatically fixed.
           git commit -am "Release v${{ needs.prepare-workflow.outputs.salt-version }}" || \