Maintenance: New issues should be unasigned

[alan-churley]

Currently all new issues are being assigned to @saragerion and myself, as a result It an be confusing to see which issues are not yet picked up,

We should modify the auto_assign-issues.yml to change this default

[bahrmichael]

Any objection to dropping the file https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/.github/auto_assign-issues.yml completely? We could re-add it again later when we need it.

[dreamorosi]

I was actually just looking into it and I think the best way would be to simply disable it by setting addAssignees to false and assignees to empty in the file you mention.

The GitHub integration is managed at the organization as far as I can see from the repo settings so, at least with my user, I can't remove it.

On the other hand, looking at the code of the integration, it seems that if the config file is not found it'll throw an error and cause the workflow to fail.

If you agree I can just push the updated file.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.