From ede16d31d99eb633630b037dc668e7c9b21ac769 Mon Sep 17 00:00:00 2001 From: ludamad Date: Mon, 9 Sep 2024 15:02:17 -0400 Subject: [PATCH] chore(ci): rerun ci when ready for review + don't allow draft merge (#8456) --- .github/workflows/ci.yml | 13 +++++++++++-- README.md | 2 +- 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 8f203febd53..78bab204d48 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -3,6 +3,11 @@ on: push: branches: [master, provernet] pull_request: + types: + - opened + - reopened + - synchronize + - ready_for_review branches-ignore: [devnet] workflow_dispatch: inputs: {} @@ -705,9 +710,10 @@ jobs: - boxes - boxes-test # - protocol-circuits-gates-report # non-blocking - if: github.event.pull_request.draft == false && always() + if: always() steps: - - name: Report overall success + - name: Report overall success (non-draft) + if: github.event.pull_request.draft == false env: # We treat any skipped or failing jobs as a failure for the workflow as a whole. FAIL: ${{ contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled') }} @@ -719,6 +725,9 @@ jobs: echo "All jobs succeeded, merge allowed." exit 0 fi + - name: Block merge (draft) + if: github.event.pull_request.draft + run: echo "Can't merge drafts." && exit 1 rerun-check: runs-on: ubuntu-20.04 diff --git a/README.md b/README.md index ae5156f1d04..cc6b62484a8 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,7 @@ Recovering if the sync is not happening with basic pull commands: - manually editing the commit variable in noir/noir-repo/.gitrepo: this needs to exist in the branch we push to, and have the same content as our base. This is similar to submodules, except instead of pointing to the final state of the module, it points to the last commit we have sync'd from, for purposes of commit replay. This can be fixed to match the commit in master after merges. -- manually editing the parent variable in noir/noir-repo/.gitrepo: this is the parent of the last sync commit on aztec side. If you get errors with a commit not being found in the upstream repo, and the commit mentioned is not the commit variable above, it might indicate this is somehow incorrect. This can happen when commit content is ported without its history, e.g. squashes +- manually editing the parent variable in noir/noir-repo/.gitrepo: this is the parent of the last sync commit on aztec side. If you get errors with a commit not being found in the upstream repo, and the commit mentioned is not the commit variable above, it might indicate this is somehow incorrect. This can happen when commit content is ported without its history, e.g. squashes. - use pull --force ONLY where you would use git reset. That is, if you really want to match some upstream noir for a purpose its fine, but you'll lose local changes (if any) ## Earthly