Create a repository
- Open Repositories and start repository creation.
- Select a personal or organization owner. Your organization role must permit creation.
- Set a name and slug, add a description, and choose the default branch.
- Review visibility before creating. A public repository can be viewed by people outside your team.
Bring in code
An empty repository needs a first commit before it has file history. Clone it to start locally, or add its HTTPS clone URL as a new remote to an existing committed project. Review your current remotes before changing them.
git remote -v
git remote add ramuvo https://ramuvo.com/git/OWNER/REPOSITORY.git
git push -u ramuvo mainBefore you continue: Replace OWNER, REPOSITORY, and main with your values. This adds a new remote; it does not replace an existing origin.
Review access and settings
Open the repository Settings tab to review the controls your role permits. Check collaborators and organization access before sharing private project URLs. Knowing a private repository URL does not grant access to it. Token scopes also cannot override repository permissions.
Keep work connected
Use issues for tasks, pull requests for proposed changes, and the project board to organize work. Releases, discussions, and roadmaps are available through their repository sections; the visible actions depend on your role.