---
title: "Git Usage"
space: "Factory Docs"
url: "https://factory.uga.edu/docs/git"
updated: "2026-11-17"
---

We use **Git** for source control across two hosting environments:

- Our self-hosted **Forgejo** instance at [git.factory.uga.edu](https://git.factory.uga.edu/).
- **GitHub**, primarily through the [UGA-Innovation-Factory](https://github.com/UGA-Innovation-Factory), [UGAMODEL](https://github.com/UGAMODEL), and [georgiaaim](https://github.com/georgiaaim) organizations.

Both platforms provide Git repository hosting and collaboration. The choice of host is primarily about **where a repository belongs operationally**, rather than a difference in how Git itself is used.

## Which Platform Should I Use?

For a **new Innovation Factory repository, default to Forgejo** unless there is a specific reason for the repository to live on GitHub.


| Repository type                                                      | Preferred host | Rationale                                                                                                                |
| -------------------------------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Lab infrastructure                                                   | **Forgejo**    | Keeps infrastructure configuration and operational code on lab-managed infrastructure.                                   |
| Innovation Factory website or other internally operated web services | **Forgejo**    | Keeps the source alongside the infrastructure we operate.                                                                |
| New internal tools and services                                      | **Forgejo**    | Default location for software primarily supporting our own environment.                                                  |
| Existing GitHub project                                              | **GitHub**     | Avoid moving an established repository without a useful reason.                                                          |
| Repository expected to receive frequent external/public access       | **GitHub**     | Allows GitHub to absorb clone/download traffic rather than using Innovation Factory-hosted bandwidth and infrastructure. |


This is a preference rather than a hard division. Repository visibility, collaborators, existing integrations, and expected traffic can all justify choosing a different host.

## Forgejo

Our internal Git service is available at [git.factory.uga.edu](https://git.factory.uga.edu/).

Forgejo is the preferred home for repositories closely coupled to the operation of the Innovation Factory. Typical examples include:

- Infrastructure and service configuration.
- Website source and deployment configuration.
- Home Assistant configuration and related cyber-physical infrastructure.
- Internal utilities and automation.
- Lab-specific software that does not benefit from being hosted externally.

Keeping these repositories on Forgejo gives us a Git service under our own administrative control and provides a natural home for code that is itself part of the lab's infrastructure.

### Example

The [IFCAT repository](https://git.factory.uga.edu/UGA-Innovation-Factory/ifcat) is hosted on Forgejo and includes Home Assistant configuration, ESPHome firmware, dashboards, documentation, and related testbed software.

## GitHub

We also maintain and contribute to repositories through several GitHub organizations:

- [UGA-Innovation-Factory](https://github.com/UGA-Innovation-Factory)
- [UGAMODEL](https://github.com/UGAMODEL)
- [georgiaaim](https://github.com/georgiaaim)

GitHub remains appropriate in two particularly common cases.

### Existing Repositories

Many projects predate the deployment of our Forgejo instance. These generally remain on GitHub rather than being migrated solely for consistency.

Moving an established repository can disrupt existing clone URLs, forks, links, CI/CD configuration, integrations, and collaborators. Unless migration provides a concrete benefit, leaving an established project where it already lives is usually simpler.

### High-Traffic or Externally Consumed Repositories

GitHub is also useful when we expect a repository to be cloned, downloaded, or accessed frequently outside the lab and have no reason to keep that traffic on Innovation Factory infrastructure.

In those cases GitHub effectively handles the public-facing repository traffic for us. This is particularly useful for software, examples, or other artifacts intended for broad distribution.

## Decision Guide

 When creating a repository, use this order of questions:

1. **Is this lab infrastructure, website code, or software primarily supporting Innovation Factory systems?**
  - Use **Forgejo** by default.
2. **Does the repository already exist on GitHub with useful history, links, collaborators, or integrations?**
  - Keep it on **GitHub** unless there is a specific reason to migrate it.
3. **Do we expect substantial or frequent external access?**
  - Consider **GitHub**, particularly when there is little value in serving that traffic from our own infrastructure.
4. **Does neither case strongly apply?**
  - Prefer **Forgejo** for a new Innovation Factory project.

## Git Workflow

The underlying Git workflow is the same regardless of which service hosts the repository.

Clone a repository:

```Shell
git clone <repository-url>
```

Create a working branch:

```Shell
git switch -c <branch-name>
```

Review and commit changes:

```Shell
git status
git add <files>
git commit -m "Describe the change"
```

Push the branch:

```Shell
git push -u origin <branch-name>
```

From there, use the hosting platform's web interface to open a pull/merge request when review is appropriate.

## Repository Practices

Regardless of hosting platform:

- Keep source, configuration, and documentation under version control when they are required to reproduce or maintain a system.
- Use meaningful commits that describe a coherent change.
- Prefer feature/fix branches and review for changes where breakage would affect shared infrastructure or other users.
- Include a useful `README.md` describing the project's purpose, setup requirements, and basic usage.
- Do **not** commit passwords, API tokens, private keys, or other secrets to a repository, including a private repository.
- Keep generated artifacts and large transient files out of Git unless they are intentionally part of the project.

## Forgejo vs. GitHub Is Not a Git Difference

The important distinction is between **Git**, the distributed version-control system, and **Forgejo/GitHub**, the services hosting repositories.

A local Git repository can generally interact with either service in the same way:

```PlainText
Developer workstation
        |
        |  git clone / fetch / pull / push
        |
        +-------------------+
        |                   |
        v                   v
     Forgejo              GitHub
 git.factory.uga.edu    github.com
```

This separation is useful to keep in mind. Choosing Forgejo does not lock the project into a special version-control workflow, and choosing GitHub does not change the fundamental Git model. The hosting decision is primarily about administration, project history, accessibility, integrations, and where we want repository traffic to be served.