Patrick Jungermann

@camilaibs We can add support for more GH event types at the entity provider. All of these, I would consider enhancements. Each event type might need a specific action. In...

It makes sense to me to check for further event types we might want to have as well and missing still.

If nobody else wants to give it a try I can have a look as well.

I have identified the following event types that seem to make sense to be added: - `RepositoryArchivedEvent`: remove registered `Location` entities from that repository - `RepositoryDeletedEvent`: remove registered `Location` entities...

I have a draft for the repo events locally. I will share a PR when it's ready.

@wanisfahmyDE you can, sure. It would make it clearer I think.

btw: Not sure if there is already another issue for making the behavior for archived repositories configurable.

@awanlin I'm currently working on PR #22344 which will change the event support and make it ready for the new backend system. In the future setup, you would add `eventsServiceRef`...

As a resolution to #21906, we will add support for additional event types including repository archived and renamed. However, this will require the event support to be enabled for the...

Workaround: Pass a file with the following content via the `--config`/`-n` option: ``` { "options": { "preset": { "name": "conventionalcommits", "commitUrlFormat": "{{host}}/{{owner}}/{{repository}}/commits/{{hash}}" } } } ```