Don't re-review when new commits are pushed (#214)

It is possible to require re-reviews when new commits are pushed via
branch protection rules, but when that setting is enabled existing
reviews are transitioned to `DISMISSED`, so we should already handle
that case with the `state === "APPROVED"` check.

src/approve.test.ts

@@ -179,23 +179,6 @@ test("when a review is commented", async () => {
   expect(createReview.isDone()).toBe(true);
 });
 
-test("when an old commit has already been approved", async () => {
-  apiMocks.getUser();
-  apiMocks.getPull();
-  apiMocks.getReviews(200, [
-    {
-      user: { login: "hmarr" },
-      commit_id: "6a9ec7556f0a7fa5b49527a1eea4878b8a22d2e0",
-      state: "APPROVED",
-    },
-  ]);
-  const createReview = apiMocks.createReview();
-
-  await approve("gh-tok", ghContext());
-
-  expect(createReview.isDone()).toBe(true);
-});
-
 test("when a review has already been approved by another user", async () => {
   apiMocks.getUser();
   apiMocks.getPull();

src/approve.ts

@@ -40,8 +40,7 @@ export async function approve(
     core.info(`Commit SHA is ${prHead}`);
 
     const alreadyReviewed = reviews.some(
-      ({ user, commit_id, state }) =>
-        user?.login === login && commit_id == prHead && state === "APPROVED"
+      ({ user, state }) => user?.login === login && state === "APPROVED"
     );
     const outstandingReviewRequest = pr.requested_reviewers?.some(
       (reviewer) => reviewer.login == login