Create sync-fork.yml

[shroffk]

I have currently created this as a test using my personal shroffk/reccaster fork... once we are happy.

@ralphlange if you have permissions on https://github.com/epics-modules you can create a fork and PAT

[shroffk]

Yay!!!
this works as expected. So we can have an automatically sync'd fork under https://github.com/epics-modules

[ralphlange]

What is the function of the 'sync-fork' branch?

[jacomago]

This is syncing, you want mirroring https://docs.github.com/en/repositories/creating-and-managing-repositories/duplicating-a-repository

[shroffk]

What is the function of the 'sync-fork' branch?

testing the sync ci jobs, I expect it should be deleted from the workflow once we are ready to merge

This is syncing, you want mirroring https://docs.github.com/en/repositories/creating-and-managing-repositories/duplicating-a-repository

maybe I am missing something, but the mirroring does not seem like a continuous thing... it performs more like a one time migration thing.

[jacomago]

Fair enough.

FYI you don't need to title WIP, you can use the draft functionality of github. Means it can't accidentaly be merged as well.

[shroffk]

@ralphlange I have tested this and it works as expected.

Should we consider creating a fork under epics-modules? do you have the privileges to create a fork and a access token?

We can then update the sync-fork.yml, replacing the shroffk with epics-modules and merge this.

[ralphlange]

I don't think we had agreement that a sync'ed fork is a good idea after all. Did we?

[shroffk]

I am fine with this just being in ChannelFinder org...but I don't see much harm in the sync fork. We can also use branch protection to ensure that the epics-modules one remains unaffected.

@ralphlange What are your opinions on this?

[ralphlange]

I have many opinions.

But as I have never used ChannelFinder or reccaster, I am not sure about their relevance.