Manuel Spigolon

Meanwhile, I have done the discord notifier, if the maintainer of the action will ship it, we will have this feature done 🎉

I have started to use it in some repositories of mine and I love it: https://github.com/Eomm/fastify-overview/blob/main/.github/workflows/release.yml I would apply the multi-user feature provided by optic in a "custom way". I...

> Unless the last step can be automated, this is a no-go :(. We have too many repositories. As solution, an GH-App that stores the secretes and centralize them. Then...

> I don't think that repo secrets can be retrieved. They can only used directly in workflows, there isn't a way to get them out of GitHub What I'm thinking...

I thought a bit about this and I think one setup-up could be: - Create a `fastifybot` npm user - Configure the `fastifybot` user in this way: - turn on...

It is already doable (not straight forward tbh) ``` const fastify = require('fastify')({ logger: true, requestIdHeader: 'jdnsndfjegrnjsdnij', genReqId() { return undefined }, }) fastify.get('/', async (request, reply) => { return...

Oh, I got it! The issue here is to choose the priority of the genId option over the header 👍🏼 Yeah, I agree! Would you like to submit a pr?

It should support both as ajv does You can switch between one or the other using the $schema property

> Did someone implement this feature ?, i have some free time and I'd like to take it up. Feel free to open a draft PR if you need some...

thank for improving the Fastify plugin ecosystem Would you like to send a Pull Request to add it to the ecosystem?