Andre_601

Also, to add to this: I previously used `draft: true` yet this didn't work either which made me update the configuration file.

I have suggestions for 2 possible ideas on how to restructure the file handling, which both have benefits but also disadvantages. ## 1) Split types up into separate files Perhaps...

Fair enough. Just thought it could be an interesting approach but there are obvious drawbacks and issues with it.

Looking back at this after a relatively long time, I still have a good feeling about using separate markdown files for the different label actions, tho now I think about...

```typescript export interface Labeled { issue: Issue; pr?: Issue; } ``` This wonders me... Would this make `issue` required? SInce it lacks the `?` which to my basic ts knowledge...

Can we still suggest new future starter workflows through issues? Or is that also on hold right now?

> I believe that asset_path is the asset/file that you want to upload: https://github.com/actions/upload-release-asset/blob/master/action.yml#L8-L10. So it is the generated file itself and I assume relative to the build environment (Similar...

I now tried creating a zip using the `zip` command in a previous command, to then upload it to the release. However, this doesn't work as I receive the following...

I use this action in a release event with type published, so the release itself is clearly available, meaning the link shouldn't be null/empty.

Like I mentioned does this action trigger on creating a release and only after it is of the type `published` meaning it is created and available. This also means that...