The repo has moved to HarnessMD/munder-difflin

[chaitanyagiri]

Munder Difflin's repo moved today, from chaitanyagiri/munder-difflin to HarnessMD/munder-difflin.

New address: https://github.com/HarnessMD/munder-difflin

Why

The project now sits under an organization instead of my personal account, so it is no longer tied to one login.

What stays the same

• Old links redirect: pages, issues, pull requests, releases and git addresses.
• Your stars, forks, open pull requests, issues and discussions all came along. You do not need to reopen anything.
• The website (https://munderdiffl.in), the downloads and the app's own updates work as before.

What you may want to do

Git follows the redirect, so nothing is broken. This is tidying.

If you have a clone of this repo, point it at the new address:

git remote -v
git remote set-url origin https://github.com/HarnessMD/munder-difflin.git

If you work from a fork, your fork's address did not change. Update only the remote that points at this repo, often called upstream:

git remote set-url upstream https://github.com/HarnessMD/munder-difflin.git

If something broke

If a link, a badge or a workflow of yours stopped working because of the move, reply here and say what you see.

[imMamdouhaboammar]

@chaitanyagiri looks like Michael moved the office, but a few boxes still have the old shipping address 😄

I checked the repo after the transfer, and there's a small migration detail worth catching

The [current README](https://github.com/HarnessMD/munder-difflin/blob/main/README.md) still references chaitanyagiri/munder-difflin in several places: the clone instructions, release links, download badge, contributor graphic, and demo video URLs

GitHub's redirects should handle the GitHub-hosted links, so there's no reason to assume those are broken

The interesting part is what happens outside GitHub

Services consuming OWNER/REPO as an identifier might handle the redirect differently. Badges, external integrations, install scripts, allowlists, and release automation are all worth checking

A quick sweep would catch the obvious references:

git grep -nF 'chaitanyagiri/munder-difflin'

I'd update the public-facing ones even where the redirect works. New contributors shouldn't have to learn the previous address just to clone the current project

There's also a less obvious detail in [GitHub's repository transfer documentation](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository)

When a repository moves from a personal account to an organization, issue assignments to users outside the receiving organization are cleared

So the issues survive the move, but some of their assigned owners might quietly disappear

For a project with an active contributor queue, that's worth a quick audit

One last thought about your reason for moving: reducing dependence on a single login

GitHub [recommends having at least two organization owners](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization), precisely because an organization with one owner still has a single-account recovery problem

I don't know how HarnessMD's ownership is configured, but I'd include that in the migration checklist too

Funny thing about moving an agent-powered office: Git can forward the mail automatically, but someone still has to check who has the keys to the building 😅