Version control system for a large project
I need to create a repository for a large game on Unity, the size of which is not limited to 1 GB. It is desirable that such a repository be free (at least at the initial stage of development). I heard that GitHub can be used for such purposes, splitting a large project into parts that will be stored in several repositories. I created the main repository with the code and a repository with images to store the project images. The code is committed normally. But when I want to commit the images to the image repository, GitBash gives me a message that the histories of the local repository (with the project) and the remote repository (with images) do not match. And therefore it is impossible to push a commit. What should I do, how to make commits to the image repository and track image changes in the main project relative to the repository with images?
Version control system for a large project
I need to create a repository for a large game on Unity, the size of which is not limited to 1 GB. It is desirable that such a repository be free (at least at the initial stage of development). I heard that GitHub can be used for such purposes, splitting a large project into parts that will be stored in several repositories. I created the main repository with the code and a repository with images to store the project images. The code is committed normally. But when I want to commit the images to the image repository, GitBash gives me a message that the histories of the local repository (with the project) and the remote repository (with images) do not match. And therefore it is impossible to push a commit. What should I do, how to make commits to the image repository and track image changes in the main project relative to the repository with images?
Version control system for a large project
I need to create a repository for a large game on Unity, the size of which is not limited to 1 GB. It is desirable that such a repository be free (at least at the initial stage of development). I heard that GitHub can be used for such purposes, splitting a large project into parts that will be stored in several repositories. I created the main repository with the code and a repository with images to store the project images. The code is committed normally. But when I want to commit the images to the image repository, GitBash gives me a message that the histories of the local repository (with the project) and the remote repository (with images) do not match. And therefore it is impossible to push a commit. What should I do, how to make commits to the image repository and track image changes in the main project relative to the repository with images?
Version control system for a large project
I need to create a repository for a large game on Unity, the size of which is not limited to 1 GB. It is desirable that such a repository be free (at least at the initial stage of development). I heard that GitHub can be used for such purposes, splitting a large project into parts that will be stored in several repositories. I created the main repository with the code and a repository with images to store the project images. The code is committed normally. But when I want to commit the images to the image repository, GitBash gives me a message that the histories of the local repository (with the project) and the remote repository (with images) do not match. And therefore it is impossible to push a commit. What should I do, how to make commits to the image repository and track image changes in the main project relative to the repository with images?
Version control system for a large project
I need to create a repository for a large game on Unity, the size of which is not limited to 1 GB. It is desirable that such a repository be free (at least at the initial stage of development). I heard that GitHub can be used for such purposes, splitting a large project into parts that will be stored in several repositories. I created the main repository with the code and a repository with images to store the project images. The code is committed normally. But when I want to commit the images to the image repository, GitBash gives me a message that the histories of the local repository (with the project) and the remote repository (with images) do not match. And therefore it is impossible to push a commit. What should I do, how to make commits to the image repository and track image changes in the main project relative to the repository with images?
Is there a Git native way to non-interactively transform a commit’s metadata to produce a new commit without touching the working tree and index?
This is a generalization of my previous question, aimed at improving my understanding of what can and cannot be done internally to Git.
Is there a way to duplicate a Git commit with different parents without first replacing?
Consider the following sequence of commands:
git, blob is a snapshot, my question is why git use this word: snapshot? It is really a copy of the source code [closed]
Closed 3 days ago.
git, blob is a snapshot, my question is why git use this word: snapshot? It is really a copy of the source code [closed]
Closed 3 days ago.
git, blob is a snapshot, my question is why git use this word: snapshot? It is really a copy of the source code [closed]
Closed 3 days ago.