Azure-devops-docs: Explain purpose of pushing to bare git repository

[mloskot]

From https://stackoverflow.com/a/49623979/151641

> It’s usually unnecessary to push local git repo to a local bare repo
> unless you want to treat the local bare repo as your remote git server.

git svn clone-ed repository can be pushed to remote repository directly.

With the advent of Azure DevOps, GitHub, suggestion of pushing to bare repo seems obsolete and possibly confusing.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: edd6cbc8-5e3b-c3a1-4672-d42510cc058b
• Version Independent ID: 8fe81fb5-7c2d-2562-5659-55fccbb3126c
• Content: Migrate from Subversion (SVN) to Git
• Content Source: docs/articles/perform-migration-from-svn-to-git.md
• Product: devops
• GitHub Login: @hkamel
• Microsoft Alias: hkamel

[steved0x]

@mloskot Thanks for your feedback, I am checking with the author to see if we need to make an update. Thank you.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ianwilliams1]

@steved0x, any update from you or the author to this issue; stale(bot) closed it.

[mloskot]

@ianwilliams1

stale(bot) closed it.

Luckily, stale bot just warned it is going to close it soon, but you're comment postponed the actual closing.

However, I'm also interested in a feedback

[ianwilliams1]

I can understand stale(bot) closing when lack of submitter response, but when it's in MSFT's (owner) queue, that's not good. Maybe give stale(bot) some AI - or better logic?

[skylee91]

OMG there is no follow up since July. Nobody working in this Docs Microsoft?

[mloskot]

@skylee91 Yes, unfortunately, this issue is not an exception. Microsoft asks the community for help in proof-reading the docs but looking at the number of open issues, well, it's very de-motivating...

[ianwilliams1]

Unfair to single out the Docs ppl; the last real update to the Jenkins tfs-plugin was 2018-08-13, over a year ago. There was a minor update to the documentation there recently in which they basically forgot about their product Azure DevOps Server in their re-branding exercise, so not counting it. 83 outstanding issues, including 27/28 failed PRs

[cxwtool]

This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.