[fix]: failing ci due to unpulled changes by previous workflow

Summary:
In the previous setup, we had both the release-logger and release-todo
workflows running and pushing changes to the repository. Obviously one
would finish executing before the other, and the changes would not have
been pulled by the incomplete job since it's already past the checkout
stage. One way to get around this would be to use the `pull` argument in
the 'commit kustomization.yaml to Github' stage. The other option would
be to trigger the workflow only if changes are made in specific
directories that the workflow is instructed to watch, and skip
otherwise.

Author: Itsfoss0

.github/workflows/release-logger.yaml

@@ -6,7 +6,6 @@ on:
       - main
     paths:
       - ".github/workflows/**"
-      - "0x3-logger/**"
 
 env:
   DOCKER_USERNAME: ${{ secrets.DOCKERHUB_USERNAME }}

.github/workflows/release-todo.yaml

@@ -5,7 +5,6 @@ on:
     branches:
       - main
     paths:
-      - ".github/workflows/**"
       - "project/**"
 
 env: