debug

0o-de-lally · Aug 4, 2024 · 553f24e · 553f24e
1 parent 8d7b8d8
commit 553f24e
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/.github/workflows/ci.yaml → .github/workflows/ci.todo b/.github/workflows/ci.yaml → .github/workflows/ci.todo
diff --git a/.github/workflows/debug.yaml b/.github/workflows/debug.yaml
@@ -20,7 +20,6 @@ env:
   DIEM_FORGE_NODE_BIN_PATH: ${{github.workspace}}/diem-node
   LIBRA_CI: 1
   MODE_0L: "TESTNET"
-  # LAST_COMMIT_MSG: ${{github.event.head_commit.message}}
 
 jobs:
   upgrades:
@@ -40,7 +39,7 @@ jobs:
       # should always run unless we know and expect the upgrade to be breaking. In that case we wither explicitly name the branch with breaking, or the commit message as "[breaking]" (for example in the PR title)
       - name: upgrade - should be backwards compatible
         run: |
-          #echo "LAST_COMMIT_MSG=$(git log $GITHUB_SHA --pretty=%B)" >> ${GITHUB_ENV}
+          echo "LAST_COMMIT=$(git log $GITHUB_SHA --pretty=%B)" >> ${GITHUB_ENV}
           echo LAST_COMMIT_MSG=${{github.event.head_commit.message}} >> ${GITHUB_ENV}
           echo LAST_COMMIT_MSG: ${{env.LAST_COMMIT_MSG}}
           echo contains breaking: ${{contains(env.LAST_COMMIT_MSG, '[breaking]')}}
@@ -57,6 +56,8 @@ jobs:
       - name: should run
         if: ${{env.BRANCH_BREAKING=='true' || env.COMMIT_BREAKING=='true'}}
         run: |
+            echo LAST_COMMIT: ${{ env.LAST_COMMIT }}
+            echo LAST_COMMIT_MSG: ${{ env.LAST_COMMIT_MSG }}
             echo BRANCH_BREAKING: ${{ env.BRANCH_BREAKING }}
             echo COMMIT_BREAKING: ${{ env.COMMIT_BREAKING }}
             echo "should run"