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

Upstream Sync #2178

Merged
merged 2 commits into from
Mar 1, 2024
Merged

Upstream Sync #2178

merged 2 commits into from
Mar 1, 2024

Conversation

thedavidweng
Copy link
Contributor

allow fork to sync with upstream automatically.

Copy link

vercel bot commented Feb 6, 2024

@thedavidweng is attempting to deploy a commit to the r3play Team on Vercel.

A member of the Team first needs to authorize it.

@pan93412
Copy link
Collaborator

pan93412 commented Mar 1, 2024

I afraid that not every forks want to sync with upstream. I will prefer to do it manually and frequently if I really want to make the fork sync.

@thedavidweng
Copy link
Contributor Author

I afraid that not every forks want to sync with upstream. I will prefer to do it manually and frequently if I really want to make the fork sync.

Fair point, but GitHub Action requires users who fork to manually enable it before it can be activated, so it is turned off by default. Having this action will help self-deploying users who do not participate in development but only use it. This is a common practice in many similar open-source repos.

@pan93412
Copy link
Collaborator

pan93412 commented Mar 1, 2024

Make sense.

@pan93412 pan93412 merged commit 1a2c3e2 into qier222:master Mar 1, 2024
1 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants