fix: Force parameter not added for keep === 0

The comparison to check if the force parameter should be supplied used the string based input argument and not the parsed number when comparing with the number 0. Thus force would always be false, even for those cases where keep === 0. This is now fixed. However, the bug highlights the need to port the project to TypeScript to more easily catch these bugs. Signed-off-by: Snorre Magnus Davøen <snorre.magnus.davoen@adventuretech.no>
bilberry-blend · Jan 20, 2023 · b8277e0 · b8277e0
1 parent 33716c8
commit b8277e0
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/dist/index.js b/dist/index.js
diff --git a/dist/index.js.map b/dist/index.js.map
diff --git a/main.js b/main.js
@@ -152,7 +152,7 @@ const main = async ({ project, account, branch, since, token, deploymentTriggerT
   let deleted = 0
   for (let i = 0; i < branchDeployments.length; i++) {
     try {
-      await deleteDeployment(project, account, token, keep === 0, branchDeployments[i])
+      await deleteDeployment(project, account, token, keepNumber === 0, branchDeployments[i])
       deleted = deleted + 1
       core.info(`🟢 Deleted deployment ${branchDeployments[i].id}`)
     } catch (e) {