I believe this should have been labelled with Documentation: devdocs but wasn't due to #27642.

Yeah I didn't label this just to see if the action worked!

Tried to re-run it, but it's still complaining about the same stuff, so I guess it's pulling from the base commit, and not top of main. Maybe if you rebase this one it'll figure itself out?

so I guess it's pulling from the base commit

is that how it ended up w/ the toolkit label?

Looks like that one is another minor issue in the config: #27644

@dstansby @QuLogic do either of you have a preference for admonition vs card for the API changes call out?

@dstansby @QuLogic do either of you have a preference for admonition vs card for the API changes call out?

To me, card feels a bit out of place. Either we regard "API changes" a proper part of the coding guidelines, in which case we should keep the original heading (optionally move that section further down). Or we regard it as a cross-ref hint (think: "if you contribute code, please consider our API changes policy as well"), in which case, I'd go with .. note::.

To me, card feels a bit out of place. Either we regard "API changes" a proper part of the coding guidelines, in which case we should keep the original heading (optionally move that section further down). Or we regard it as a cross-ref hint (think: "if you contribute code, please consider our API changes policy as well"), in which case, I'd go with .. note::.

So this change was motivated by the link out to the API guidelines getting kinda buried:

I tried a card and I did not like it. Trying a highlight approach now, will post back.

Changed this PR to just change the link on the PR template so it can go in quickly, moving the docs changes to a different PR