Terminal and git
Running commands in the project directory, and a git panel that tells you where you stand before you push.
The terminal
Runs in your project directory. Start a dev server, run a build, install a dependency — the ordinary things, in the place they need to happen.
Files can be dropped into it, which saves typing a path.
On Windows it runs through cmd.exe; see
Windows setup for what that implies.
The terminal needs a licence.
Terminals ask before they open
A shell started in a folder can pick up that folder’s own settings, so FEWD opens a terminal only in a folder you have trusted. The first time, it asks Trust this folder? and shows the shell it is about to start. Not now opens no terminal and leaves the project editable. Closing the window stops the terminals, dev servers and installs FEWD started.
See Security notices explained.
The git panel
A modal, from the git icon on the bottom bar.
It opens by telling you where you stand: how many commits ahead of your remote you are, how many behind, and what is uncommitted.
That is the thing worth having. A panel that only offers a Push button lets you find out you were nine commits behind at the moment it fails.
Getting changes
Get changes pulls. Before it does, you can see what is waiting — so accepting somebody’s work is a decision rather than a surprise.
Pushing
Write a message, press Push.
Push refuses when you are behind. Get the changes first. This is not FEWD being cautious on your behalf; it is what git would do, said earlier and more clearly.
A commit you made by hand in the terminal pushes from here perfectly well.
Commit and push need a licence.
Git and trusted folders
Git does not run in a folder you have not trusted, because a project that arrives
with its own .git folder brings its own Git settings, and Git obeys them. A
project you downloaded with From GitHub… can use Git straight away. For any
other folder, FEWD asks once, and the Git panel offers Trust this folder if you
said Not now.
Before a project opens
If Preferences → Check for changes on opening a project is on, FEWD checks the remote as a project opens and tells you if there is anything waiting.
That dialog can be cancelled — Escape works — and cancelling leaves whatever you had open exactly as it was.
Cloning a private repository
From GitHub… on the welcome screen signs you in with a device code, lists the repositories you can push to, and clones the one you choose to a folder you pick. See Opening a project.
Working with a client in the same repository
Where a client is publishing content edits from a git-based CMS into the same repository, your commits and theirs meet in git rather than fighting over a document.
Pull before you start rather than after you have finished. Their edits are ordinary commits to content files, so this is normal git hygiene rather than anything special to these apps.