-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync public forks for NCIPangea #10
Conversation
superseded by CCBR/.github#10
superseded by CCBR/.github#10
not needed because forks can be manually updated with a button click from the fork's main page already
@kelly-sovacool ... can we also add new PRs for NCIPangea/RENEE and NCIPangea/XAVIER to remove their gh-actions which are getting replaced. |
@kelly-sovacool ... can you change the firing time to early morning ... I think you used 11:47 for testing purposes. |
Yep can do! I picked a kinda random minute because they recommend not doing the beginning of the hour since many people do that and it overloads the runners. |
Actually I just remembered these times are in UTC, which is 5 hours ahead of EST, so 11:47 UTC = 06:47 EST. Is this a good time @kopardev? |
I already opened them: (remember all changes should occur in the upstream repo) |
Did not realize the UTC part... leave it as-is :) |
Makes sense! Good to know. |
A new action to supersede the individual sync-fork actions we have in place for XAVIER and RENEE. This uses a matrix to run
gh repo sync
on all public forks we specify in this workflow's matrix.@kopardev: I think you will need to go into this repo's settings and update theEdit: actually it looks like my token worked for NCIPangea! I'm unsure if it'll work for the ABCS org, but we can cross that bridge when we get there. I believe the creator of the token must have write access to all forks for it to work.SYNC_FORK_TOKEN
secret with a new token with repo & workflow scopes. This token will need to be configured to work for CCBR, NCIPangea, and any other organizations that will have forks synced automatically. I don't think my token will work for NCIPangea because the option didn't come up when I tried to configure SSO after creating the token.Resolves https://github.com/CCBR/kelly_log/issues/16