Skip to content
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

Workflow to sync with Google's repo #70

Closed
wants to merge 1 commit into from

Conversation

fredericsimard
Copy link

This workflow will sync this forked repo with the source one, every Sunday @ midnight ETC.

This workflow will sync this forked repo with the source one, every Sunday @ midnight ETC.
@fredericsimard fredericsimard added the enhancement New feature or request label Jan 30, 2025
@fredericsimard fredericsimard self-assigned this Jan 30, 2025
@fredericsimard fredericsimard changed the title First commit Workflow to sync with Google's repo Jan 30, 2025
@davidgamez
Copy link
Member

I'm not sure if the full process will work smoothly. The reason is that a commit to master in this fork will impact the diff between the fork and the source repositories. Any branch out of the master in the fork will contain the action file and potentially appear in future PRs. I would suggest to have this action in a different repository to keep the fork as clean as possible.

My apologies if I might be missing something obvious in the fork sync process as I haven't test myself this kind of scenario

@fredericsimard
Copy link
Author

fredericsimard commented Jan 31, 2025

Yeah, I had the same thought but there is a --force flag I didn’t use that would erase all commits no matter if it is behind or ahead. As far as I understood it, without this flag if it's not possible to just sync because there are commits ahead, it will fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants