Guilherme Kammsetzer

Just FYI I worked on this issue for a while and tried solving it by adding a ts-node register call instead of throwing [here](https://github.com/fastify/fastify-autoload/blob/master/index.js#L166), that would handle all require calls...

After investigating this issue for a while I think we got a couple of options: 1- Get the `fetch-metadata` action output and use it on `github-action-merge-dependabot` action. This would be...

I'll take a better look at the optic release action. That's probably the best way to do it. About 2, I don't think I get the limitations/need for a token....

Im working on this issue

Hey, is this issue still valid? If so, is there a way to get a new repro link? Looks like the old link was removed (returning 404 now). I tried...

> [dependabot/fetch-metadata#270](https://github.com/dependabot/fetch-metadata/pull/270). This PR has a compatibility score badge 95% in the body of the PR, but the output of the fetch-metadata action shows compatibility score 0. https://github.com/nearform/the-fastify-workshop/actions/runs/3180518436/jobs/5184208481#step:2:23 That's because...

@wenqiglantz this use case is now supported by enabling the [automerge option](https://github.com/fastify/github-action-merge-dependabot#use-github-auto-merge) on the action. This will allow the action to add 1 approve and the PR will be merged...