electron
feat: add upstream `sysroot_scripts` monitoring
This adds some auto-monitoring to prevent massive script drift. Action runs every two weeks.
Successful run: https://github.com/electron/debian-sysroot-image-creator/actions/runs/13845024913
New issue: https://github.com/electron/debian-sysroot-image-creator/issues/52
@dsanders11
In this case I'm guessing an issue is desirable because it can be referenced in an associated PR to land the upstream changes?
yes, exactly.
Addressed changes - let me know if i missed anything! As to the Slack event - I suppose we could fire to upgrades? I'm not opposed but also potentially would bias towards @mentioning the team in the issue instead. What do you think?
As to the Slack event - I suppose we could fire to upgrades? I'm not opposed but also potentially would bias towards @mentioning the team in the issue instead. What do you think?
Historically I feel like there's a lot of noise in our collective GitHub notifications so not sure that would improve visibility too much.
I guess it's just a matter of how priority it is. If it's something that should be done ASAP, I'd opt for firing a Slack message to ensure it gets seen. If it's something that can wait for a while then I think it's fine to do the issue.
@dsanders11 I think i'll leave it as an issue and then add a team @mention then - I'd classify it as fairly low-urgency and something that can definitely wait until someone gets to it.