It kind of is, you push to a repository which is not on your computer. Force push protection stops you from rewriting history and default branch on github is protected by default and requires an option to be disabled (or well used to, I use gitea these days).

▲

bawolff an hour ago | parent | next [-]

The backup part of that is that you are sending a copy of your code to a separate server (github).

It has nothing to do with git. Making a copy on a separate server would still be a backup even if you weren't using git. Using git without pushing your repo somewhere else would not be a backup.

	▲	himata4113 an hour ago \| parent [-]
		see response to charcircuit below.

▲

charcircuit 2 hours ago | parent | prev [-]

>you push to a repository which is not on your computer

That is not a mandatory part of using source control. Modern source control can work entirely on your own computer.

>Force push protection stops you from rewriting history

This doesn't always exist and usually there are ways to disable it.

▲

himata4113 an hour ago | parent [-]

restic/borg is not a backup application because you backup to a folder in the same directory called `.git`... doesn't sound right does it? git (and other source control systems) in every shape and form are a backup tool. In fact, a lot of people use git as a backup system for their OS configuration.

	▲	bawolff an hour ago \| parent [-]
		> restic/borg is not a backup application because you backup to a folder in the same directory called `.git`... doesn't sound right does it? It does sound right. Obviously the world isn't black and white, and whether something is a backup depends on what threats you are backing up against. Backing up in case of disk failure looks different then if you want your backup to survive a nuclear war. But ultimately yes, if you configure restic/borg to backup to a different directory on the same disk (and not even different access control), that is not a backup.