A self-hosted Git server versus a bare repository: you need pull requests

Описание и применение

Перенос репозитория из bare‑сервера в AngusGit позволяет использовать pull‑requests, обзоры кода и защиту веток, улучшая совместную работу.

Задача

A bare Git repository lacks pull requests, review, and web interface, making collaboration hard when code changes need review before merging into main.

Результат

The repository migration enables pull requests, code review, issue linking, and branch protection, improving collaboration and code quality.

Рабочий процесс

• Create an empty repository on AngusGit (leave README, .gitignore, license unchecked).
• Clone the existing bare repository with git clone --bare.
• Push all branches with git push --all and all tags with git push --tags to the new AngusGit repo.
• Rename local main branch if needed (git branch -m master main).
• Have teammates update their remote URL with git remote set-url origin <new-url> and fetch.
• Use AngusGit’s web UI to open pull requests, review, and merge.
• Enable branch protection on main to enforce PRs before merge.

Доказательства

A bare repository stores only Git data. It has no working files you can edit.

Источник

Open the repository in a browser, go to the Branches tab, and on the new branch's row click Compare with default branch. Then click Create Pull Request.

Источник

The first command uses --all to push every branch. The second uses --tags to push every tag.

Источник

Create an empty repository on AngusGit (leave Add a README file, Add .gitignore, and Choose a license unchecked).

Источник