Urgent.News

What's breaking now, across thousands of outlets.

Tech

Move a GitHub project to an internal Git host: import or push, then follow upstream

This article explains how to move a GitHub project onto an intranet AngusGit, whether to import or to push, and how to keep following upstream afterward. After reading it, you can choose by asking whether you will still follow upstream: if you will not, and you only need the current code, use Import repository ; if you need the history or you will merge upstream, clone locally, set GitHub as…

Moving a GitHub project to an internal Git host involves two main options: importing or pushing. The choice depends on whether you want to follow upstream and keep the original commit history. If you only need the current code and don't need the history or plan on merging upstream, use the import method. If you need the history or will merge upstream, clone locally, set GitHub as upstream, create a new empty repository as origin, and push.

To begin the import process, sign in to AngusGit first. On the AngusGit sidebar, navigate to Repositories and click Import at the top right. Enter the source URL (HTTPS address), owner, and repository name. Turn on Make this repository private if only the team should see it, then click Begin import. The server will fetch the repository anonymously and create a new import repository with the same files and default branch. The AngusGit server can only reach GitHub if it can connect at the time of import.

If you need the history and plan on merging upstream, you'll need to clone the GitHub repository on your computer, then push it to a new empty repository on AngusGit. Create an empty repository on AngusGit without adding a README file, .gitignore, or choosing a license. This ensures the target repository is empty. Do not use an existing repository as the target to avoid adding commits that would reject the push due to mismatched histories.

Do not clone the imported repository as it would add commits that cannot be merged with the upstream.

To push the main branch and tags, first clone the GitHub repository on a machine that can reach both GitHub and the intranet AngusGit. Rename the GitHub remote to upstream and add the AngusGit repository as the new origin. Fetch and push the main branch and tags from the upstream (GitHub) to the AngusGit origin. This allows you to keep a local clone of the repository and sync with upstream later.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

High-Performance Ingress & Network Architecture: Building Resilience at Scale

Webhook ingress gateways have to absorb bursty traffic from third-party senders and stay responsive when some of those connections are slow or hostile.

  • Employ HTTP/3 and QUIC for faster, resilient webhook gateways
  • Defend against slow-connection attacks like Slowloris and Slow-Read
  • Use memory-mapped ring buffers to absorb traffic bursts

More from Saturday 31 October →