Post #1251390
2026-04-07 09:04 UTC
@hikhvar Consider that screenshots are typically cropped, or include highlights, or blur parts to hide information that is private or uninteresting, etc. So, automating such screenshot updates is an "interesting" task.
Consider further that you may have hundreds of screenshots that are all affected by a change of one line of CSS, rendering your "let's ask a human" approach impractical.
And sadly, not thinking about this sort of thing is exactly what I mean by not giving a fuck about docs.
Replies (2)
-
@larsmb@mastodon.online 2026-04-07 09:47
@xahteiwi @hikhvar As far as I know, our doc team updates those before release. (How much of that is already also automated already I don't quite know. Probably at least in progress.)
-
@hikhvar@norden.social 2026-04-07 09:52
@xahteiwi was that different when people created the code? If changing CSS is a problem in the process, you must instruct everyone to not change it. In the best case you have verified this via a CI test in your pipeline. If so, the agent will see this signal similarly to your new hire will learn about it.