Taras Mankovski

I tried. I'm not able to override it because Backstage projects are a monorepo with tsconfig.json at the root. I created an example project to show you https://github.com/taras/backstage-openapi-client-scaffolding

It's part of our publish actions. The action will automatically call npm deprecate when it encounters this this property in package.json

There is work happening in Effection repo around this https://github.com/thefrontside/effection/pull/638#pullrequestreview-961004094

@cowboyd I captured the ideas that I wanted to put down on paper. Can you please continue in Extensibility section to describe what this API might look like?

It appears there is an RFC in Backstage https://github.com/backstage/backstage/issues/11082

Progressively opting into GitHub processing, 1. Start by adding your Github instance to your app-config.yaml ```yaml locations: - type: github-organization-discovery location: https://github.com ``` You added location, but nothing ingested because...

If you don't need discovery, then you would use this, ```yaml locations: - type: github-organization location: https://github.com/thefrontside - type: github-organization location: http://github.com/microstates ```

On deno 2.1.7, I couldn't get @mortezaPRK's code to work, but I got @felipecrs's code running with @mortezaPRK's monkey patch. The following is the final version for reference. ```ts import...

Hey @DanielSharkov, What change did you make in your tweak? > Wouldn’t it be more correct to just use Promise.race to handle the first completed promise and cancel the unfinished...

@kissmikijr did you start working on this? I've been collaborating with SourceGraph on a blog post on how to use Batch Changes to onboard projects Backstage. We've also been talking...