pushing and pulling #150709
Unanswered
oceanblue42
asked this question in
New to GitHub
pushing and pulling
#150709
Replies: 1 comment 2 replies
-
|
Yeah you need to properly configure
Here is what you need to modify in So from now on, follow this:
Please mark this as helpful answer if this works! |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I create a project in vs code on local machine. I create a blank repo on github. I push my project to github. I make that repo a template. Another user then makes a repo from that template. from that repo he creates a codingspace. user adds two remotes to codigspace. 1) origin which points to his repo 2) template which points to my repo.
User needs to be able to pull from the template and push and pull to origin. We are trying to automate the process.
heres what devcontainer contains:
devcontainer.json
here's what .git/config contains on startup:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
ignorecase = true
[user]
name = Bob
email = rle@gmail.com
[remote "template"]
url = https://github.com/oceanblue42/python_class
fetch = +refs/heads/:refs/remotes/template/
[branch "master"]
remote = template
merge = refs/heads/master
I wanted to use rebase for the template pulls and merge for push and pull from/to origin. I keep getting divergent branches.
we just want to be able to pull from template and push/pull from origin using the UI in codingrooms.
the template (oceanblue42/python_class is know in advanced. The name of the other repo is not and will need to added through the ui. Is there a way to update "postCreateCommand": "git config --local commit.gpgsign false && git config --local branch.master.mergeOptions '--allow-unrelated-histories' && bash ./.devcontainer/setup.sh"
in the devcontainer to take care of the rest and once and forall resolve divergent path issue. the following should then work in the ui:
syncronize changes should work and not try to push back onto template
Beta Was this translation helpful? Give feedback.
All reactions