-
Notifications
You must be signed in to change notification settings - Fork 4
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 code between ubiquity/devpool-directory
and ubiquity/devpool-directory-private
#25
Comments
@rndquu This up for grabs? |
Yes, you may setup code sync between https://github.com/ubiquity/devpool-directory and your forked instance of https://github.com/rndquu/devpool-directory-private-test for testing purposes and open a PR, I will check how it works with https://github.com/ubiquity/devpool-directory-private then |
/start |
Tips:
|
# These linked pull requests are closed: <a href="https://github.com/ubiquity/devpool-directory/pull/1193">#1193</a> |
I think we should use a git submodule. Basically we set up the private Directory to import all the contents of the public Directory, and then we overwrite the behavior of what needs to be different. |
Ideally all of the changes should be made in https://github.com/ubiquity/devpool-directory, in particular:
So that we could simply:
|
There are 2 repositories which collect issues available for contributors:
The issue is that we somehow need to sync code changes between https://github.com/ubiquity/devpool-directory and https://github.com/ubiquity/devpool-directory-private. We can't simply fork https://github.com/ubiquity/devpool-directory-private from https://github.com/ubiquity/devpool-directory and use github UI since private repos can't be synced.
What should be done:
Possible solution described here
The text was updated successfully, but these errors were encountered: