Change to release env for syncing examples

[nitbharambe]

• To confirm if the release bot is set up to have only current repo level access and not access to org level repos.

I see refresh lock and linter dependencies is missing and needed. Ill add it separately

[figueroa1395]

We don't do releases, do we need this change?

Also,

To confirm if the release bot is set up to have only current repo level access and not access to org level repos.

Have you checked this box yet?

[mgovers]

if we only are allowed to sync on main (which makes sense), can we please add a CI check that none of the files in PGM main are edited directly in this repo?

[nitbharambe]

As an extra check then? Since I removed token in 7155201, editing is not possible. (And later writing needs release token)

if we only are allowed to sync on main (which makes sense), can we please add a CI check that none of the files in PGM main are edited directly in this repo?

[mgovers]

As an extra check then?

yes, if someone provides a new workshop contribution, and they edit files they should not be editing (as they will be overwritten on main when the syncer runs), there should be a CI check telling them that

[nitbharambe]

We don't do releases, do we need this change?

Because only the release environment contains write permissions now.

Have you checked this box yet?

This is now an unblocking question since I added repositories: power-grid-model-workshop to scope the token for sync-examples.

But nice to know about its scope regardless. @TonyXiang8787 Does the release token give access to current repository or to all repositories of PowerGridModel?

[TonyXiang8787]

@nitbharambe the secret itself (private key and id) gives release access to all PGM repo's. The generated token, I don't know.

[TonyXiang8787]

@nitbharambe is this ready to merge?

[nitbharambe]

Ready to merge