Anton Iakimov

This is a useful part of security guide: https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference: 1. The GITHUB_TOKEN...

"Fine-grained" token didn't work with user owner - git fails to push: ``` remote: Permission to status-im/nimbus-eth2.git denied to status-im-auto. fatal: unable to access 'https://github.com/status-im/nimbus-eth2/': The requested URL returned error:...

Looks like Deploy key is actually might be useful for us: 1. https://stackoverflow.com/questions/76888117/how-can-i-push-changes-to-a-private-repository-using-github-actions 2. https://tabris.com/using-deploy-keys-on-github-actions/ 3. https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#set-up-deploy-keys

No update since January. There are 2 options: - Deploy keys - Create a github user with limited permissions just for this task

So no way to run bash from GOW on Win7_64? Maybe any workaround present?

Multi-EL is documented officially without syaing it's unstable/beta: https://nimbus.guide/eth1.html#running-multiple-execution-clients @etan-status, @tersec, @jakubgs, maybe we can try running multi-EL again? BTW, we are running multi-EL on nimbus.mainnet: https://github.com/status-im/infra-nimbus/blob/42cfc2958a39cc6ec316f1f46d45189cf9ff995f/ansible/group_vars/nimbus.mainnet.yml#L81

Hi everyone! Is it still not possible?

@flexsurfer, @cammellos, can you help with review?

@churik, can you please help to test this PR?

Yes, it is relevan, sorry, missed you comment. @churik, can you help with testing?