User guidesIT services in ColombiaeCloud help and resources

ECLOUD / 07

Connect GitHub over SSH and prepare modules

Organise code, configure access and verify your changes reached the correct repository.

Version 4.0 · review proposal · 28 Oct 2026

eCloud guides
  1. Your computer
  2. Git repository
  3. AppCloud testing

Arrows point to real controls. Enlarge any detail. Names and options may vary by version and account permissions.

01

Understand what you are connecting

Git tracks code changes. GitHub hosts the repository, a project folder with that history. SSH authenticates your computer using a private and a public key.

This procedure is for the authorised code maintainer, not someone who only uses Odoo. You need Git, OpenSSH, your GitHub account and repository permissions.

The SSH attempt returns Permission denied (publickey); GitHub CLI with HTTPS is then used.

First authenticate your computer with SSH and verify access. Then upload code. Configure AppCloud access to the repository separately.

02

01 · Prepare a key without replacing others

Linux Terminal example; use Git Bash on Windows. First check git --version and ssh -V. If missing, ask for installation from official sources.

  1. Check existing keys with ls -la ~/.ssh. Consult your administrator before replacing an approved key.
  2. For a new key, run the example using your own email. Never overwrite existing files.
  3. Choose a new file path if the default is occupied. Add a protective passphrase.
  4. Load the private key into the agent, adjusting the path if you chose another name.
ssh-keygen -t ed25519 -C "usuario@example.com"
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519
03

02 · Register only the public key

  1. Display cat ~/.ssh/id_ed25519.pub. The .pub ending matters.
  2. In GitHub open your profile → Settings → SSH and GPG keys → New SSH key.
  3. Give the computer a recognisable title, choose an authentication key and paste the complete public key.
  4. Select Add SSH key and complete GitHub’s requested authentication.
Public key · .pub

Register this in GitHub.

Private key · no .pub

Keep it protected on your computer. Never paste it into GitHub, email or manuals.

Instructional illustration · fictional data
GitHub → Settings → SSH and GPG keys
Action
New SSH key
Title
portatil-demo
Key type
Authentication Key
Key
Paste only the complete contents of id_ed25519.pub.

Add SSH key saves the public key. The private key stays on your device.

04

03 · Verify SSH before uploading files

Run ssh -T git@github.com. On the first connection compare the fingerprint with GitHub’s official fingerprints before accepting.

Expected result: GitHub recognises your user and reports successful authentication without shell access. This is normal: you are connecting Git, not opening a remote desktop or server shell.

For Permission denied (publickey), check ssh-add -l, the registered public key and the authorised account. Resolve this before uploading. Organisations using SSO may require key authorisation.

ssh -T git@github.com
Instructional illustration · fictional data
Identity check
Before accepting
Compare the fingerprint with official documentation.
Correct response
GitHub recognises YOUR username and reports that shell access is unavailable.
If it fails
ssh-add -l lists loaded keys; check account and public key.
Reference capture · Spanish interface

Permission denied (publickey)

Permission denied (publickey)
Select 1 to highlight the instruction.

01Authentication failed. Check the remote user, loaded key and registered public key. Fix access before repeating push.

05

04 · Open the correct repository

  1. Open your organisation’s GitHub repository. If creating one, make it private and follow company rules.
  2. Under Code → Local → SSH, copy its address.
  3. In an authorised working folder run git clone SSH_ADDRESS, replacing the placeholder. Enter the created folder with cd FOLDER_NAME.
  4. If a local copy already exists, use it; do not clone over it or initialise it again.
  5. Check git remote -v and git branch --show-current. SSH addresses generally begin with git@github.com:. Confirm the agreed branch before editing.

Local SSH and the AppCloud form are separate: the eCloud build form shown requests an HTTPS URL and, when needed, a read token.

Instructional illustration · fictional data
GitHub → Code → Local → SSH
SSH
git@github.com:empresa-demo/odoo-addons.git
HTTPS
https://github.com/empresa-demo/odoo-addons.git

Fictional addresses: copy your own repository URLs. SSH authenticates your computer; AppCloud uses independent read access.

06

05 · Organise, review and send changes

AppCloud expects addons/technical_name/__manifest__.py. Each module must be unpacked in its folder. requirements.txt is optional for required dependencies. Never upload databases, VPN profiles, private keys or tokens.

  1. Copy only authorised modules compatible with your Odoo version.
  2. If needed, set repository-level identity with git config user.name "Your name" and git config user.email "user@example.com".
  3. Review git status and git diff.
  4. Stage only approved paths. The example stages addons; stage requirements.txt explicitly if changed.
  5. Review staged changes before creating a commit (a change record). Push only to the approved branch.
git add addons/
git diff --cached --stat
git diff --cached --check
git commit -m "Update approved modules"
git push -u origin main

The example uses main; adapt it to your branch. If rejected, review branch rules or remote changes with the maintainer; do not use --force. In GitHub verify the commit and folders. Uploading code does not publish it to production.

Instructional illustration · fictional data
What each command does
git status / git diff
Shows changed files and changes before staging.
git add addons/
Stages those files for the next commit.
git diff --cached --stat / --check
Summarises staged changes and detects whitespace issues.
git commit
Records the local change; does not send it yet.
git push
Sends to the remote branch. Verify the commit in GitHub.
Reference capture · Spanish interface

addons

addons
Select 1 to highlight the instruction.

01Check the repository root with pwd and ls. requirements.txt is optional and belongs at the root when additional dependencies are needed.

Help and references

Available options depend on the service, version and your account permissions.

Request support ↗

GitHub · SSH ↗

GitHub · Fingerprints ↗