Fredrik Adelöw
Fredrik Adelöw
What was the error message you got when you tried to use the file directly? As in, ```yaml auth: providers: github: development: $include: github-app-backstage-myapp-credentials.yaml ```
@Apaachai oh dang, I just realized too late after merging - does it work as well for you in all of those browsers if the overflow is set on `rings`...
Hey, thanks for the detailed report! In particular, the duplicate rows in the `refresh_state_references` table was a superb thing to spot, because that could hint at some concurrent updates trampling...
Yes, manual deletion is always an option if you are sure it should indeed be gone, for both cases. Regarding 2, yeah a small cleanup script of sorts might help,...
Hi! Did you try scrolling (with touch, or the mouse scroll wheel) in the different quadrants? This is a behavior that was intentionally introduced in https://github.com/backstage/backstage/pull/7075 . If that doesn't...
Closing this as the first versions of this are in alpha already, and the rest of the work is tracked in other issues.
Hey, you'll need to run `yarn build:api-reports` and commit the results as well whenever you make public API changes (see the build log).
I can resolve my own comments sure! Sounds like it's complex enough that a re-review might be in place. Either way I see that the build is red and there...
@jamieklassen Just a mild ping to remove the stale label, no rush
Remember to run `yarn build:api-reports` and commit all api-report.md changes as well. In general, often a review may be deferred as long as the build is not green.