# PiTrac repo is getting a new home

-# The code is moving soon from `jamespilgrim/PiTrac` → `PiTracLM/PiTrac`.

**TL;DR:** We're transferring the repo to the new **@PiTracLM** organization. Old links will keep working for now, but after the change below is completed, please update your local `origin` (or `upstream` if you forked) to the new URL. We will let folks know when it's done.

**New repo:** https://github.com/PiTracLM/PiTrac  
**Old repo:** https://github.com/jamespilgrim/PiTrac  
**Packages (DEB):** https://pitraclm.github.io/packages/

## Why the change?
- Moving to a github **organization** gives us better, more granular permission control for maintainers and contributors.
- It lets us grow with multiple repos under the **PiTrac** name (docs, tooling, packages, etc.).
- We’ve also launched our new **DEB package hosting**: https://pitraclm.github.io/packages/

> Heads up: GitHub will redirect `git clone/fetch/push` from the old path to the new one, but it’s best practice to update your remote so your tooling and scripts point to the right place.

## Update your Git remote

### 1) See which protocol you use
Run:
```bash
git remote -v
```
Look at the `origin` URL:
- If it starts with `git@github.com:` → you’re using **SSH**
- If it starts with `https://github.com/` → you’re using **HTTPS**

**Which should I pick?**
- Stick with what you’re already using.
- Choosing fresh? **SSH** is great for regular contributors (no passwords/PAT prompts once your SSH key is set up). **HTTPS** can be simpler behind strict networks or for occasional contributions.

### 2) Update `origin` to the new repo

**SSH**
```bash
git remote set-url origin git@github.com:PiTracLM/PiTrac.git
```

**HTTPS**
```bash
git remote set-url origin https://github.com/PiTracLM/PiTrac.git
```

### 3) Verify
```bash
git remote -v
```