Skip to content
Etonymdocs

Publish a folder

Publishing sends a branch to a remote for the first time and connects the two, so that Push and Pull work from then on.

  • The folder is a Git repository with at least one commit. See Commit and push.
  • You have created an empty repository on your Git host: no README, no license, no .gitignore. A host refuses the first push into a repository that already has files. Etonym does not create the repository or open your host’s page for you.
  • You have the new repository’s address. Your host shows it right after you create the repository.
  1. In the Git tab, choose Publish…. Without a remote, it takes the place of Fetch, Pull and Push. Until the branch has a commit, it is turned off, and its tooltip says Commit first.
  2. A Repository URL field opens in the Git tab, with the reminder Use an empty repository: no README or license. Paste the address there.
  3. Press Enter.

Etonym adds the address as the remote origin and pushes the current branch under the same name, so the branch now follows the remote one. When it is done, Etonym shows Published main. (with your branch name), and Push and Pull take the place of Publish….

If the push fails, Etonym removes origin again and keeps the address in the field, so you can fix the problem and try again.

A branch you create in Etonym starts without a remote branch, so the Git tab shows Publish for it. When the repository already has a remote, Publish pushes the branch right away, without asking for an address.

Message What to do
This folder is already connected to another repository. The folder already has a remote named origin. Use Push.
That doesn’t look like a repository address. Copy the HTTPS or SSH address from the repository’s page. Copy the full HTTPS or SSH address again from your host.
That repository already has commits (a README or license, for example). Use an empty repository, or clone this one instead. Create a new, empty repository on your host and publish to it. To work on the existing one, clone it instead.
Could not reach the remote… Check the address, the network and your sign-in.