jprdonnelly/docs
1
0
Fork 0
mirror of synced 2026-01-10 09:02:35 -05:00
Code Issues Projects Releases Wiki Activity

Merge pull request #12076 from StelioKontosXBL/patch-4

Browse Source 
Fix windows tip appearing in code block
This commit is contained in:
mc
2021-11-18 09:44:16 +00:00
committed by GitHub
parent 2014034e24 9111b4d489
commit 61ca48eaa6
1 changed files with 50 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files

91
content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
View File

@@ -17,65 +17,74 @@ shortTitle: Splitting a subfolder
If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Change the current working directory to the location where you want to create your new repository.
3. Clone the repository that contains the subfolder.
```shell
$ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY-NAME</em>
```
4. Clone the repository that contains the subfolder.
```shell
$ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY-NAME</em>
```
4. Change the current working directory to your cloned repository.
```shell
$ cd <em>REPOSITORY-NAME</em>
```
```shell
$ cd <em>REPOSITORY-NAME</em>
```
5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information:
- `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository.
- `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository.
{% windows %}
{% windows %}
{% tip %}
{% tip %}
**Tip:** Windows users should use `/` to delimit folders.
**Tip:** Windows users should use `/` to delimit folders.
{% endtip %}
{% endtip %}
{% endwindows %}
{% endwindows %}
```shell
$ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
# Filter the specified branch in your directory and remove empty commits
> Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
> Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
```
The repository should now only contain the files that were in your subfolder(s).
```shell
$ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
# Filter the specified branch in your directory and remove empty commits
> Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
> Ref 'refs/heads/<em>BRANCH-NAME</em>' was rewritten
```
The repository should now only contain the files that were in your subfolder(s).
6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
{% tip %}
{% tip %}
**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
{% endtip %}
{% endtip %}
8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
```shell
$ git remote -v
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (fetch)
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (push)
```
```shell
$ git remote -v
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (fetch)
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY-NAME</em>.git (push)
```
9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
```shell
git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git
```
```shell
git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git
```
10. Verify that the remote URL has changed with your new repository name.
```shell
$ git remote -v
# Verify new remote URL
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (fetch)
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (push)
```
```shell
$ git remote -v
# Verify new remote URL
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (fetch)
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/NEW-REPOSITORY-NAME</em>.git (push)
```
11. Push your changes to the new repository on {% data variables.product.product_name %}.
```shell
git push -u origin <em>BRANCH-NAME</em>
```
```shell
git push -u origin <em>BRANCH-NAME</em>
```