Axel Hecht

@dagda1 Do you have a proposal on how to integrate this with the template editor? Re security concerns, if we have those, I'd rather have them on the client than...

Nudge

Leaving some personal opinions here: I'd prefer for all docs to be in the pontoon repo. I'm not sure how much impact localizing docs should have on our decision. I...

We should probably try on a dummy doc. Things I'd like to see tested are various cross references, indices, and search.

Tested this locally, and works. Also the code looks like what I expected. CC @drodil @freben PS: The PR state is weird? No reviewers assigned, no uffizi? Haven't looked at...

One way to fix this would be to split `start` into `build` (naming things) and `start`? FWIW, this is reproducible on demo, https://demo.backstage.io/search?query=radar&types%5B%5D=software-catalog

1.27.2 is out including this fix, and it works for me locally (my 1.26+ migration isn't fully done yet)

I just played around with the API a bit, and maybe this is what we're looking for? ```graphql query { repository(owner:"backstage", name:"community-plugins") { ref(qualifiedName:"refs/heads/main") { name compare(headRef:"04kash:use-knip") { aheadBy behindBy...

I suspect the problem here is the fetch-depth in https://github.com/backstage/community-plugins/blob/3e04330a2aee795e6286fa19266bfbf7e09cd466/.github/workflows/ci.yml#L31, paired with the fetch-depth of 1 on the main branch. Which means that commits between main and the merge base...

Taking a stab at this in #1522 . Given each iterations takes approvals, maybe that's not the best first-pr?