An interval seems to be left running which delays node from exiting for 30 seconds

[ajrussellsap]

When using the project-piper-action from a workflow on a GitHub Enterprise server, I consistently see a 30-second delay when node exits. This has also been noted by colleagues working on completely different projects. This issue seems to happen when no github.com token is specificed and, after some investigation I have tracked it down to being caused by this fetch statement:

https://github.com/SAP/project-piper-action/blob/main/src/fetch.ts#L11

The debug output from a workflow step shows that the delay happens after the step has finished doing everything:

A trace of the action shows that there is something (possibly an interval) that runs every second for 30 seconds which prevents node from exiting:

I wasn't able to determine the precise reason why this fetch command leaves something running every second for the next 30 seconds but I found that using a HEAD request prevented the issue from happening. I have created a pull request for this:

#219

I was not able to use my own fork of project-piper-action directly in my workflow - due to the policy of the GitHub Enterprise server - but I was able to create a workflow that patches the index.js file before it gets called and this fixes the problem. I would be happy to share that workflow privately if it helps.

Anyway, I would very grateful if you could resolve this issue (with my PR or any other way that you see fit) as it is adds about 5 minutes to the run time of every workflow for me and quite a few colleagues.

Many thanks

Alex