Git authentication fails
Do not use your browser login as proof that terminal Git is configured. Do not embed a replacement token in the remote URL.
- Verify the remote URL matches the repository’s HTTPS clone URL.
- Check that your account can access the repository.
- Check token expiry and the repository, capability, branch, and path restrictions.
- If a credential helper saved an old token, update that credential using the helper’s own controls.
A push is rejected
Check whether the remote branch contains changes you have not fetched, whether branch/path rules allow your update, and whether your credential can write. Fetch and inspect the history before integrating other changes. For an extension publish that already created the repository, retry with Push to Ramuvo rather than Publish Local Repository.
The editor keeps waiting for sign-in
Links belong to the current authorization attempt and should be kept private. Tokens expire after one hour; reconnect if an existing session expires.
- Keep the editor window that started authorization open.
- Complete browser consent and allow the return callback.
- If that fails, copy the sign-in link from the result page and run Ramuvo: Complete Sign-in.
- Cancel an old attempt before starting a new one.
An Action or deployment fails
- Open the failed run or deployment and inspect the first failed step.
- Check the selected branch, workflow file, environment, and command.
- Confirm required secret names are configured for that environment.
- Review the runner and workflow messages before retrying.
A page module could not be loaded
Reload the browser tab. Tabs kept open during a release can refer to old JavaScript module filenames. The error screen offers Reload page for this case. If a new load still fails, check connectivity and include the missing asset URL in a report.
Prepare a useful problem report
Record the affected page or command, steps to reproduce, expected result, actual result, and exact error. For editor problems include the editor and extension versions and whether the host is local, SSH, or a container. Remove tokens, cookies, authorization links, private files, and secret values from logs and screenshots.