About LidPush

The short version

LidPush is a Windows desktop app. You sign in with GitHub once, pick a repository that you already own, point at a project folder, and LidPush handles the rest: it cleans the copy, scans it for secrets, shows you the site in your browser, and pushes it with one click.

The entire point is that you never have to touch git. Everything git normally demands from you — the installation, the configuration, the commands, the errors — is handled behind the scenes by the app. You keep your attention on your project, not on the plumbing.

The problem it was built for

There is a huge group of people who never push code to GitHub, and it is rarely because they do not want to. It is because git is miserable to start with. Someone builds something — a school project, a portfolio, a finished static site — the folder is sitting right there on their machine, and the repository already exists on GitHub. Good. All that is missing is the upload.

And that is exactly where it stops, because to upload, git asks you to climb a staircase with this on every step:

• installing Git and finding the right download among the noise
• making your terminal actually recognise git (PATH, anyone)
• setting a username and email for the first time
• learning init, add, commit, remote, push and getting the order right
• working out .gitignore the hard way, after the first disaster commit
• creating a personal access token with the right scopes — classic or fine-grained?
• and finally meeting the error message that makes no sense on your first push

Any single one of those steps is enough to stop a beginner. Most people do not fail at git because they are incapable. They fail because git never cared to explain itself in the first place.

That is the gap LidPush exists for: you already have a repository, you already have a folder, and the only missing step is the upload.

The alternatives were not built for this

• GitHub's web upload. Drag a folder into the browser and it chokes: files have a size limit, nested folders become a chore, and there is no way to preview or clean a project before it goes up.
• GitHub Desktop. It is a better wrapper, but you still have to think in git's grammar — commits, remotes, branches, conflicts. The whole model is aimed at people who already speak git.
• VS Code and plugins. They still require the git binary and configuration to exist on your machine before anything works.

All of them answer a different question. Nobody builds a tool around this one: "I have a folder and a repo — put the folder in the repo, and do the scary parts for me." That is the only question LidPush answers, and it is very good at it.

Why the app is deliberately small

LidPush does not try to be another git client. It does not manage branches, merge, rebase, rewrite history, or handle ten remotes. Git is already excellent at all of that, and power users should keep using it for those jobs.

LidPush keeps exactly one job: upload files to a repository you already have. Because it does fewer things, it does them properly:

• the upload always happens on a clean copy, never your real folder
• junk like node_modules and build caches never reach the repo
• secrets get flagged before anything leaves your machine
• you actually see the site in a browser before a single file is sent

What happens on every push

1. Sign in. A normal GitHub OAuth flow. The token is stored in Windows Credential Manager and never shown to the interface.
2. Pick the repository. Your repositories are listed, and you choose the one the folder belongs to.
3. A temporary copy. LidPush copies your project to a temp folder. Your original folder is not touched at any point.
4. Cleaning. It removes dependency folders, build outputs, caches, lock files, OS junk and git leftovers, so your repo ends up tidy.
5. Secret scan. It reads every text file and looks for GitHub tokens, AWS and Stripe keys, private key blocks and generic API_KEY= patterns.
6. Preview. The site opens in your browser and the file list shows what will be uploaded and what was flagged.
7. Push. One button. The app handles git itself with libgit2 — no separate Git installation required.

After the push you get a summary: files uploaded, files cleaned, total size, and lines of code. Every push is recorded in your history so you can look back at what went up and when.

Why you are safe while using it

• Your folder never changes. Everything happens on a temporary copy.
• Secrets are caught before upload, not after someone else finds them.
• The token is invisible — stored in Windows Credential Manager, inside an app that uses a random port and a one-time session secret for its local API.
• No extra software on your machine. Git is built into the app through libgit2, so there is no installation to fight with first.

A real example

Say you finished a portfolio site: a static build with a large assets folder — images and maybe a video, around 300 MB in total. The site works locally, and you are proud of it. You want it on GitHub because that is where projects live.

The web upload refuses once a file passes the size limit. Git could actually do it, but to use git you would first walk the staircase from earlier — install it, configure it, initialise, authenticate, only then push. That is easily ten commands and, for a first-timer, at least one error that ends the attempt.

With LidPush: sign in, pick the repo, select the folder, preview it, push. Ten minutes after opening the app, the repository has the site — clean of node_modules, clean of secrets, and your local folder exactly as it was. That difference in effort is the entire reason the app exists.

What LidPush will not do

Being honest about the edges matters more than pretending. LidPush is not a solution to every git problem:

• it is not a full git client — no rebasing, squashing, history editing or conflict resolution
• it does not create repositories — the repo must already exist
• it handles one project folder at a time, purposefully
• it is a Windows app for now

What it is made of

A short technical tour, written quickly. LidPush is a Tauri v2 desktop app with a React + TypeScript frontend. Behind it sits an embedded Axum (Rust) HTTP server that starts on a random port every launch and requires a one-time session secret. Git operations run through git2-rs (libgit2), so no Git installation is needed on your system. Your GitHub token lives in Windows Credential Manager via the keyring crate, and push history is stored as metadata in a Neon PostgreSQL database — no code, no file contents, no credentials ever reach it.

Who made it

LidPush is built by Lidprex Labs, the development team at Lidprex. It is open source under the Apache-2.0 license, and the entire codebase is on GitHub. If something is wrong, missing, or plain frustrating, open an issue there — the project is small on purpose, and real problems from real users are how it gets better.