[code-infra] Automate team sync on about page

[brijeshb42]

Summary

Scheduled triggers weekly on Monday. Can be triggered manually as well from https://github.com/mui/material-ui/actions
Automatically deletes any images as well as adds a summary for people whose images are missing.

[brijeshb42]

I may have missed something about why we still have the manual sync script. So feel free to ignore if there is a specific reason for that.

[code-infra-dashboard]

Deploy preview

https://deploy-preview-48794--material-ui.netlify.app/

Bundle size

Bundle	Parsed size	Gzip size
@mui/material	0B(0.00%)	0B(0.00%)
@mui/lab	0B(0.00%)	0B(0.00%)
@mui/private-theming	0B(0.00%)	0B(0.00%)
@mui/system	0B(0.00%)	0B(0.00%)
@mui/utils	0B(0.00%)	0B(0.00%)

Details of bundle changes

---

Check out the code infra dashboard for more information about this PR.

[Janpot]

I may have missed something about why we still have the manual sync script. So feel free to ignore if there is a specific reason for that.

Not sure this is the exact reason, but historically, it tends to be prone to breakage when things change on hibob side. Checking in the file manually adds an extra level of review. And tbh, if we're going to do it at build time, I'd rather move all data fetching from code-infra to this repo.

edt: a useful addition could be a check whether a photo/flag is present for the employee. This is something that has been breaking in the past when data updated in hibob.

[brijeshb42]

I'd rather move all data fetching from code-infra to this repo

I like current simplicity where code-infra handles the hard part, ie, keeping the hibob token, which it already has for a bunch of other services, so why not one more and core docs does a simple fetch.

check whether a photo/flag is present for the employee

Hmm. Photo fetching seems to be the main blocker I think for this PR. We can't reliably directly use one from hibob (even if it has one) without caching it somewhere. Also, we have to ensure there exists a pic for each each during the build.

[Janpot]

I think the main issue is that seemingly harmless changes in hibob (update someones name, country, add someone...) can break the build. It has happened before, where an accent was corrected in a name and suddenly the name of the photo doesn't match up anymore. Keeping the sync explicit contains this brittleness to a single PR.

[brijeshb42]

Updated the PR to instead automate the process so we can still validate changes before merging.

[Janpot]

In this setup, does it still make sense to keep the logic in code-infra? We could keep the token in GHA secrets?

[brijeshb42]

Yeah. We can move that here.

[brijeshb42]

On a second note, moving this here then won't allow someone to create the PR manually, if that is something we still want to keep.

[Janpot]

On a second note, moving this here then won't allow someone to create the PR manually, if that is something we still want to keep.

ok, yeah. Let's wait then.