Skip to content

πŸ“¨ The ultimate agentic social media scheduling tool πŸ€–

fix(staging): streamline preflight push verification process

Enno Gelhaus7e86a129bdde
diff --git a/.github/workflows/staging-conflicts.yml b/.github/workflows/staging-conflicts.yml
index b1fc421a3..cafaf1e2c 100644
--- a/.github/workflows/staging-conflicts.yml
+++ b/.github/workflows/staging-conflicts.yml
@@ -47,12 +47,11 @@ jobs:
ssh-keyscan -t ed25519 github.com >> ~/.ssh/known_hosts
echo "GIT_SSH_COMMAND=ssh -i $HOME/.ssh/staging_merge -o IdentitiesOnly=yes" >> "$GITHUB_ENV"
+ # `git push --dry-run` exercises the exact path the real push takes.
+ # A bare `ssh -T` does not, since GIT_SSH_COMMAND applies only to git.
- name: Preflight push
run: |
git remote set-url origin "[email protected]:${{ github.repository }}.git"
- ssh -T [email protected] 2>&1 | tee /tmp/ssh.log || true
- grep -q "successfully authenticated" /tmp/ssh.log || {
- echo "::error::deploy key did not authenticate"; exit 1; }
git push --dry-run origin HEAD:staging
echo "push path verified"
@@ -170,4 +169,4 @@ jobs:
if: steps.probe.outputs.conflicted == 'true'
run: |
git remote set-url origin "[email protected]:${{ github.repository }}.git"
- git push origin HEAD:staging
+ git push origin HEAD:staging
\ No newline at end of file