Add explicit bareRepository configuration when pushing bare mirror

[jdknight]

Why:

Was following the instructions outlined in Detaching a fork and noticed that step 5 was failing for me.

What's being changed (if available, include any code snippets, screenshots, or gifs):

If a user has configured bareRepository=explicit in their configuration, the push operation in this example will fail with the message:

fatal: cannot use bare repository '<path>.git' (safe.bareRepository is 'explicit')

By adding -c "safe.bareRepository=all" to the default instruction set, this should prevent issues for users who have bareRepository configured.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@jdknight Thanks so much for opening a PR! I'll get this triaged for review ✨

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[nguyenalex836]

@jdknight Thank you for your patience while our SME team reviewed! 💛 Our SMEs reviewed and responded with the following:

---

The problem they're trying to fix sounds real to me, but I think their solution is a bit complicated. The git-config(1) manual page has this to say about safe.bareRepository setting's explicit value:

explicit: Git only works with bare repositories specified via the top-level --git-dir command-line option, or the GIT_DIR environment variable (see git(1)).

So, instead of:
git -c "safe.bareRepository=all" push --mirror https://github.com/EXAMPLE-USER/FORK-NAME.git

I think the correct answer would be something more like:
git --git-dir https://github.com/EXAMPLE-USER/FORK-NAME.git push --mirror

Those will both do the same thing in practice, but this version is getting there without needing to override a setting.

---

If you are able to update your PR to match what our SME provided, we will be happy to get this merged ✨ thank you!

[jdknight]

• Tweaked the command to use --git-dir <bare> over moving (cd) into the bare before trying to push up the mirror.
• This drops the requirements of cding in and out of the bare repository.
• Tweaked FORK-NAME to just FORK to minimize the longer command length in an attempt to fit the command on a single line.

[github-actions]

This PR has been automatically closed because there has been no response to to our request for more information from the original author. Please reach out if you have the information we requested, or open a new issue to describing your changes. Then we can begin the review process.

[nguyenalex836]

@jdknight Apologies on behalf of our bot! Your latest updates are being reviewed by our SME team, and I'll ping you here as soon as I have a response from them 💛