CINXE.COM

<!doctype html> <html class="no-js" lang="nb" data-content_root="./"> <head><meta charset="utf-8"/> <meta name="viewport" content="width=device-width,initial-scale=1"/> <meta name="color-scheme" content="light dark"><meta name="viewport" content="width=device-width, initial-scale=1" /> <meta property="og:title" content="Versjonskontrollintegrasjon" /> <meta property="og:type" content="website" /> <meta property="og:url" content="https://docs.weblate.org/no/latest/vcs.html" /> <meta property="og:site_name" content="Weblate" /> <meta property="og:description" content="Weblate currently supports Git(with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion, Bitbucket Cloud pull requests, Bitbucket Data Center p..." /> <meta property="og:image:width" content="1146" /> <meta property="og:image:height" content="600" /> <meta property="og:image" content="https://docs.weblate.org/no/latest/_images/social_previews/summary_vcs_b454b50f.png" /> <meta property="og:image:alt" content="Weblate currently supports Git(with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion, Bitbucket Clou..." /> <meta name="description" content="Weblate currently supports Git(with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion, Bitbucket Cloud pull requests, Bitbucket Data Center p..." /> <meta name="twitter:card" content="summary_large_image" /> <meta property="fb:app_id" content="741121112629028" /> <meta property="fb:page_id" content="371217713079025" /> <meta name="twitter:site" content="@WeblateOrg" /> <link rel="index" title="Index" href="genindex.html" /><link rel="search" title="Søk" href="search.html" /><link rel="next" title="Weblate’s REST API" href="api.html" /><link rel="prev" title="Frequently Asked Questions" href="faq.html" /> <link rel="canonical" href="https://docs.weblate.org/no/latest/vcs.html" />  <title>Versjonskontrollintegrasjon - Weblate 5.11 documentation</title> <link rel="stylesheet" type="text/css" href="_static/pygments.css?v=8f2a1f02" /> <link rel="stylesheet" type="text/css" href="_static/styles/furo.css?v=354aac6f" /> <link rel="stylesheet" type="text/css" href="_static/graphviz.css?v=4ae1632d" /> <link rel="stylesheet" type="text/css" href="_static/copybutton.css?v=76b2166b" /> <link rel="stylesheet" type="text/css" href="_static/styles/furo-extensions.css?v=302659d7" /> <link rel="stylesheet" type="text/css" href="https://weblate.org/static/vendor/font-source/source-sans-3.css" /> <link rel="stylesheet" type="text/css" href="https://weblate.org/static/vendor/font-source/source-code-pro.css" /> <style> body { --color-code-background: #f8f8f8; --color-code-foreground: black; --font-stack: "Source Sans 3", sans-serif; --font-stack--monospace: "Source Code Pro", monospace; --color-brand-primary: #1fa385; --color-brand-content: #1fa385; } @media not print { body[data-theme="dark"] { --color-code-background: #202020; --color-code-foreground: #d0d0d0; --font-stack: "Source Sans 3", sans-serif; --font-stack--monospace: "Source Code Pro", monospace; --color-brand-primary: #1fa385; --color-brand-content: #1fa385; } @media (prefers-color-scheme: dark) { body:not([data-theme="light"]) { --color-code-background: #202020; --color-code-foreground: #d0d0d0; --font-stack: "Source Sans 3", sans-serif; --font-stack--monospace: "Source Code Pro", monospace; --color-brand-primary: #1fa385; --color-brand-content: #1fa385; } } } </style><script async type="text/javascript" src="/_/static/javascript/readthedocs-addons.js"></script><meta name="readthedocs-project-slug" content="weblate-nb-no" /><meta name="readthedocs-version-slug" content="latest" /><meta name="readthedocs-resolver-filename" content="/vcs.html" /><meta name="readthedocs-http-status" content="200" /></head> <body> <script> document.body.dataset.theme = localStorage.getItem("theme") || "auto"; </script> <svg xmlns="http://www.w3.org/2000/svg" style="display: none;"> <symbol id="svg-toc" viewBox="0 0 24 24"> <title>Contents</title> <svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 1024 1024"> <path d="M408 442h480c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8H408c-4.4 0-8 3.6-8 8v56c0 4.4 3.6 8 8 8zm-8 204c0 4.4 3.6 8 8 8h480c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8H408c-4.4 0-8 3.6-8 8v56zm504-486H120c-4.4 0-8 3.6-8 8v56c0 4.4 3.6 8 8 8h784c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8zm0 632H120c-4.4 0-8 3.6-8 8v56c0 4.4 3.6 8 8 8h784c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8zM115.4 518.9L271.7 642c5.8 4.6 14.4.5 14.4-6.9V388.9c0-7.4-8.5-11.5-14.4-6.9L115.4 505.1a8.74 8.74 0 0 0 0 13.8z"/> </svg> </symbol> <symbol id="svg-menu" viewBox="0 0 24 24"> <title>Menu</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather-menu"> <line x1="3" y1="12" x2="21" y2="12"></line> <line x1="3" y1="6" x2="21" y2="6"></line> <line x1="3" y1="18" x2="21" y2="18"></line> </svg> </symbol> <symbol id="svg-arrow-right" viewBox="0 0 24 24"> <title>Expand</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather-chevron-right"> <polyline points="9 18 15 12 9 6"></polyline> </svg> </symbol> <symbol id="svg-sun" viewBox="0 0 24 24"> <title>Light mode</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1" stroke-linecap="round" stroke-linejoin="round" class="feather-sun"> <circle cx="12" cy="12" r="5"></circle> <line x1="12" y1="1" x2="12" y2="3"></line> <line x1="12" y1="21" x2="12" y2="23"></line> <line x1="4.22" y1="4.22" x2="5.64" y2="5.64"></line> <line x1="18.36" y1="18.36" x2="19.78" y2="19.78"></line> <line x1="1" y1="12" x2="3" y2="12"></line> <line x1="21" y1="12" x2="23" y2="12"></line> <line x1="4.22" y1="19.78" x2="5.64" y2="18.36"></line> <line x1="18.36" y1="5.64" x2="19.78" y2="4.22"></line> </svg> </symbol> <symbol id="svg-moon" viewBox="0 0 24 24"> <title>Dark mode</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1" stroke-linecap="round" stroke-linejoin="round" class="icon-tabler-moon"> <path stroke="none" d="M0 0h24v24H0z" fill="none" /> <path d="M12 3c.132 0 .263 0 .393 0a7.5 7.5 0 0 0 7.92 12.446a9 9 0 1 1 -8.313 -12.454z" /> </svg> </symbol> <symbol id="svg-sun-with-moon" viewBox="0 0 24 24"> <title>Auto light/dark, in light mode</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1" stroke-linecap="round" stroke-linejoin="round" class="icon-custom-derived-from-feather-sun-and-tabler-moon"> <path style="opacity: 50%" d="M 5.411 14.504 C 5.471 14.504 5.532 14.504 5.591 14.504 C 3.639 16.319 4.383 19.569 6.931 20.352 C 7.693 20.586 8.512 20.551 9.25 20.252 C 8.023 23.207 4.056 23.725 2.11 21.184 C 0.166 18.642 1.702 14.949 4.874 14.536 C 5.051 14.512 5.231 14.5 5.411 14.5 L 5.411 14.504 Z"/> <line x1="14.5" y1="3.25" x2="14.5" y2="1.25"/> <line x1="14.5" y1="15.85" x2="14.5" y2="17.85"/> <line x1="10.044" y1="5.094" x2="8.63" y2="3.68"/> <line x1="19" y1="14.05" x2="20.414" y2="15.464"/> <line x1="8.2" y1="9.55" x2="6.2" y2="9.55"/> <line x1="20.8" y1="9.55" x2="22.8" y2="9.55"/> <line x1="10.044" y1="14.006" x2="8.63" y2="15.42"/> <line x1="19" y1="5.05" x2="20.414" y2="3.636"/> <circle cx="14.5" cy="9.55" r="3.6"/> </svg> </symbol> <symbol id="svg-moon-with-sun" viewBox="0 0 24 24"> <title>Auto light/dark, in dark mode</title> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1" stroke-linecap="round" stroke-linejoin="round" class="icon-custom-derived-from-feather-sun-and-tabler-moon"> <path d="M 8.282 7.007 C 8.385 7.007 8.494 7.007 8.595 7.007 C 5.18 10.184 6.481 15.869 10.942 17.24 C 12.275 17.648 13.706 17.589 15 17.066 C 12.851 22.236 5.91 23.143 2.505 18.696 C -0.897 14.249 1.791 7.786 7.342 7.063 C 7.652 7.021 7.965 7 8.282 7 L 8.282 7.007 Z"/> <line style="opacity: 50%" x1="18" y1="3.705" x2="18" y2="2.5"/> <line style="opacity: 50%" x1="18" y1="11.295" x2="18" y2="12.5"/> <line style="opacity: 50%" x1="15.316" y1="4.816" x2="14.464" y2="3.964"/> <line style="opacity: 50%" x1="20.711" y1="10.212" x2="21.563" y2="11.063"/> <line style="opacity: 50%" x1="14.205" y1="7.5" x2="13.001" y2="7.5"/> <line style="opacity: 50%" x1="21.795" y1="7.5" x2="23" y2="7.5"/> <line style="opacity: 50%" x1="15.316" y1="10.184" x2="14.464" y2="11.036"/> <line style="opacity: 50%" x1="20.711" y1="4.789" x2="21.563" y2="3.937"/> <circle style="opacity: 50%" cx="18" cy="7.5" r="2.169"/> </svg> </symbol> <symbol id="svg-pencil" viewBox="0 0 24 24"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1" stroke-linecap="round" stroke-linejoin="round" class="icon-tabler-pencil-code"> <path d="M4 20h4l10.5 -10.5a2.828 2.828 0 1 0 -4 -4l-10.5 10.5v4" /> <path d="M13.5 6.5l4 4" /> <path d="M20 21l2 -2l-2 -2" /> <path d="M17 17l-2 2l2 2" /> </svg> </symbol> <symbol id="svg-eye" viewBox="0 0 24 24"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1" stroke-linecap="round" stroke-linejoin="round" class="icon-tabler-eye-code"> <path stroke="none" d="M0 0h24v24H0z" fill="none" /> <path d="M10 12a2 2 0 1 0 4 0a2 2 0 0 0 -4 0" /> <path d="M11.11 17.958c-3.209 -.307 -5.91 -2.293 -8.11 -5.958c2.4 -4 5.4 -6 9 -6c3.6 0 6.6 2 9 6c-.21 .352 -.427 .688 -.647 1.008" /> <path d="M20 21l2 -2l-2 -2" /> <path d="M17 17l-2 2l2 2" /> </svg> </symbol> </svg> <input type="checkbox" class="sidebar-toggle" name="__navigation" id="__navigation"> <input type="checkbox" class="sidebar-toggle" name="__toc" id="__toc"> <label class="overlay sidebar-overlay" for="__navigation"> <div class="visually-hidden">Hide navigation sidebar</div> </label> <label class="overlay toc-overlay" for="__toc"> <div class="visually-hidden">Hide table of contents sidebar</div> </label> <a class="skip-to-content muted-link" href="#furo-main-content">Skip to content</a> <div class="page"> <header class="mobile-header"> <div class="header-left"> <label class="nav-overlay-icon" for="__navigation"> <div class="visually-hidden">Toggle site navigation sidebar</div> <i class="icon"><svg><use href="#svg-menu"></use></svg></i> </label> </div> <div class="header-center"> <a href="index.html"><div class="brand">Weblate 5.11 documentation</div></a> </div> <div class="header-right"> <div class="theme-toggle-container theme-toggle-header"> <button class="theme-toggle"> <div class="visually-hidden">Toggle Light / Dark / Auto color theme</div> <svg class="theme-icon-when-auto-light"><use href="#svg-sun-with-moon"></use></svg> <svg class="theme-icon-when-auto-dark"><use href="#svg-moon-with-sun"></use></svg> <svg class="theme-icon-when-dark"><use href="#svg-moon"></use></svg> <svg class="theme-icon-when-light"><use href="#svg-sun"></use></svg> </button> </div> <label class="toc-overlay-icon toc-header-icon" for="__toc"> <div class="visually-hidden">Toggle table of contents sidebar</div> <i class="icon"><svg><use href="#svg-toc"></use></svg></i> </label> </div> </header> <aside class="sidebar-drawer"> <div class="sidebar-container"> <div class="sidebar-sticky"><a class="sidebar-brand" href="index.html"> <div class="sidebar-logo-container"> <img class="sidebar-logo" src="_static/logo-text.svg" alt="Logo"/> </div> </a><form class="sidebar-search-container" method="get" action="search.html" role="search"> <input class="sidebar-search" placeholder="Søk" name="q" aria-label="Søk"> <input type="hidden" name="check_keywords" value="yes"> <input type="hidden" name="area" value="default"> </form> <div id="searchbox"></div><div class="sidebar-scroll"><div class="sidebar-tree"> <p class="caption" role="heading"><span class="caption-text">User docs</span></p> <ul class="current"> <li class="toctree-l1"><a class="reference internal" href="user/basic.html">Weblate basics</a></li> <li class="toctree-l1"><a class="reference internal" href="user/profile.html">Registration and user profile</a></li> <li class="toctree-l1"><a class="reference internal" href="user/translating.html">Oversetting med Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="user/files.html">Downloading and uploading translations</a></li> <li class="toctree-l1"><a class="reference internal" href="user/glossary.html">Ordliste</a></li> <li class="toctree-l1"><a class="reference internal" href="user/checks.html">Checks and fixups</a></li> <li class="toctree-l1"><a class="reference internal" href="user/search.html">Søking</a></li> <li class="toctree-l1"><a class="reference internal" href="workflows.html">Translation workflows</a></li> <li class="toctree-l1"><a class="reference internal" href="faq.html">Frequently Asked Questions</a></li> <li class="toctree-l1 current current-page"><a class="current reference internal" href="#">Versjonskontrollintegrasjon</a></li> <li class="toctree-l1"><a class="reference internal" href="api.html">Weblate’s REST API</a></li> <li class="toctree-l1"><a class="reference internal" href="wlc.html">Weblate-klient</a></li> <li class="toctree-l1"><a class="reference internal" href="python.html">Weblate’s Python API</a></li> </ul> <p class="caption" role="heading"><span class="caption-text">Application developer guide</span></p> <ul> <li class="toctree-l1"><a class="reference internal" href="devel/starting.html">Starting with internationalization</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/integration.html">Integrating with Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/gettext.html">Translating software using GNU gettext</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/sphinx.html">Translating documentation using Sphinx</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/html.html">Translating HTML and JavaScript using Weblate CDN</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/third-party.html">Localization libraries and packages</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/alerts.html">Translation component alerts</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/community.html">Building a translators community</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/translations.html">Managing translations</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/review.html">Reviewing strings</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/share.html">Promoting the translation</a></li> <li class="toctree-l1"><a class="reference internal" href="devel/reporting.html">Translation progress reporting</a></li> </ul> <p class="caption" role="heading"><span class="caption-text">Administrator docs</span></p> <ul> <li class="toctree-l1 has-children"><a class="reference internal" href="admin/install.html">Oppsettsinstruks</a><input class="toctree-checkbox" id="toctree-checkbox-1" name="toctree-checkbox-1" role="switch" type="checkbox"/><label for="toctree-checkbox-1"><div class="visually-hidden">Toggle navigation of Oppsettsinstruks</div><i class="icon"><svg><use href="#svg-arrow-right"></use></svg></i></label><ul> <li class="toctree-l2"><a class="reference internal" href="admin/install/docker.html">Installing using Docker</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/venv-debian.html">Installing on Debian and Ubuntu</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/venv-suse.html">Installing on SUSE and openSUSE</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/venv-redhat.html">Installing on RedHat, Fedora and CentOS</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/venv-macos.html">Installing on macOS</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/source.html">Installing from sources</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/openshift.html">Installing on OpenShift</a></li> <li class="toctree-l2"><a class="reference internal" href="admin/install/kubernetes.html">Installing on Kubernetes</a></li> </ul> </li> <li class="toctree-l1"><a class="reference internal" href="admin/deployments.html">Weblate deployments</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/upgrade.html">Upgrading Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/backup.html">Sikkerhetskopiering og flytting av Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/auth.html">Identitetsbekreftelse</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/auth.html#two-factor-authentication">Two-factor authentication</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/access.html">Tilgangskontroll</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/projects.html">Oversettelsesprosjekter</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/languages.html">Language definitions</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/continuous.html">Kontinuerlig oversettelse</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/licensing.html">Licensing translations</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/translating.html">Oversettelsesprosess</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/checks.html">Checks and fixups</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/machine.html">Automatiske forslag</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/addons.html">Tillegg</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/memory.html">Oversettelsesminne</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/config.html">Oppsett</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/sample.html">Sample configuration</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/management.html">Management commands</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/announcements.html">Kunngjøringer</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/componentlists.html">Komponentlister</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/optionals.html">Optional Weblate modules</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/customize.html">Tilpasning av Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/admin.html">Håndteringsgrensesnitt</a></li> <li class="toctree-l1"><a class="reference internal" href="admin/support.html">Getting support for Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="legal.html">Legal documents</a></li> </ul> <p class="caption" role="heading"><span class="caption-text">Contributor docs</span></p> <ul> <li class="toctree-l1"><a class="reference internal" href="contributing/index.html">Contributing to Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/communication.html">Weblate Contributor Communication Guidelines</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/start.html">Starting contributing code to Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/code.html">Weblate source code</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/debugging.html">Debugging Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/internals.html">Weblate internals</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/addons.html">Developing add-ons</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/frontend.html">Weblate frontend</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/issues.html">Reporting issues in Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/tests.html">Weblate testsuite and continuous integration</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/schemas.html">Data schemas</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/release.html">Releasing Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/security.html">Security and privacy</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/modules.html">Contributing to Weblate modules</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/about.html">Om Weblate</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/license.html">Lisens</a></li> <li class="toctree-l1"><a class="reference internal" href="contributing/trademark.html">Weblate Trademark Guidelines</a></li> </ul> <p class="caption" role="heading"><span class="caption-text">File formats</span></p> <ul> <li class="toctree-l1"><a class="reference internal" href="formats.html">Localization file formats</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/android.html">Android string resources</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/apple.html">Apple iOS-strenger</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/appstore.html">Metadatafiler for programbutikk</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/arb.html">ARB File</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/csv.html">CSV files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/dtd.html">DTD files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/excel.html">Excel Open XML</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/flatxml.html">Flat XML files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/fluent.html">Fluent format</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/formatjs.html">Format.JS JSON file</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/gettext.html">GNU gettext PO (Portable Object)</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/go-i18n.html">go-i18n JSON files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/gotext.html">gotext JSON files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/gwt.html">GWT-egenskaper</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/html.html">HTML files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/i18next.html">i18next JSON files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/idml.html">IDML Format</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/ini.html">INI translations</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/innosetup.html">Inno Setup INI translations</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/java.html">Java-egenskaper</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/joomla.html">Joomla translations</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/json.html">JSON files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/laravel.html">PHP-strenger for Laravel</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/markdown.html">Markdown-filer</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/mi18n.html">draggable/i18n lang files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/moko.html">Mobile Kotlin resources</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/odf.html">OpenDocument Format</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/php.html">PHP-strenger</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/qt.html">Qt Linguist .ts</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/resourcedict.html">ResourceDictionary files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/resx.html">.NET resource files (RESX, RESW)</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/ruby.html">Ruby YAML files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/stringsdict.html">Stringsdict-format</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/subtitles.html">Subtitle files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/tbx.html">TermBase eXchange format</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/txt.html">Tekstfiler</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/webextension.html">WebExtension JSON</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/winrc.html">Windows RC files</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/xliff.html">XLIFF</a></li> <li class="toctree-l1"><a class="reference internal" href="formats/yaml.html">YAML files</a></li> </ul> <p class="caption" role="heading"><span class="caption-text">Change history</span></p> <ul> <li class="toctree-l1"><a class="reference internal" href="changes.html">Weblate 5.11</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-10-4">Weblate 5.10.4</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-10-3">Weblate 5.10.3</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-10-2">Weblate 5.10.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-10-1">Weblate 5.10.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-10">Weblate 5.10</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-9-2">Weblate 5.9.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-9-1">Weblate 5.9.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-9">Weblate 5.9</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-8-4">Weblate 5.8.4</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-8-3">Weblate 5.8.3</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-8-2">Weblate 5.8.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-8-1">Weblate 5.8.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-8">Weblate 5.8</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-7-2">Weblate 5.7.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-7-1">Weblate 5.7.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-7">Weblate 5.7</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-6-2">Weblate 5.6.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-6-1">Weblate 5.6.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-6">Weblate 5.6</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-5-5">Weblate 5.5.5</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-5-4">Weblate 5.5.4</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-5-3">Weblate 5.5.3</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-5-2">Weblate 5.5.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-5-1">Weblate 5.5.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-5">Weblate 5.5</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-4-3">Weblate 5.4.3</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-4-2">Weblate 5.4.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-4-1">Weblate 5.4.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-4">Weblate 5.4</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-3-1">Weblate 5.3.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-3">Weblate 5.3</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-2-1">Weblate 5.2.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-2">Weblate 5.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-1-1">Weblate 5.1.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-1">Weblate 5.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-0-2">Weblate 5.0.2</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-0-1">Weblate 5.0.1</a></li> <li class="toctree-l1"><a class="reference internal" href="changes.html#weblate-5-0">Weblate 5.0</a></li> <li class="toctree-l1"><a class="reference internal" href="changes/v4.html">Weblate 4.x series</a></li> <li class="toctree-l1"><a class="reference internal" href="changes/v3.html">Weblate 3.x series</a></li> <li class="toctree-l1"><a class="reference internal" href="changes/v2.html">Weblate 2.x series</a></li> <li class="toctree-l1"><a class="reference internal" href="changes/v1.html">Weblate 1.x series</a></li> <li class="toctree-l1"><a class="reference internal" href="changes/v0.html">Weblate 0.x series</a></li> </ul> <p class="caption" role="heading"><span class="caption-text">Indices and tables</span></p> <ul> <li class="toctree-l1"><a class="reference internal" href="genindex.html">Index</a></li> <li class="toctree-l1"><a class="reference internal" href="py-modindex.html">Modulindex</a></li> </ul> </div> <div id="furo-sidebar-ad-placement" class="flat" data-ea-publisher="readthedocs" data-ea-type="readthedocs-sidebar" data-ea-manual="true" ></div> </div> </div> </div> </aside> <div class="main"> <div class="content"> <div class="article-container"> <a href="#" class="back-to-top muted-link"> <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"> <path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8v12z"></path> </svg> <span>Back to top</span> </a> <div class="content-icon-container"> <div class="view-this-page"> <a class="muted-link" href="https://github.com/WeblateOrg/weblate/blob/main/docs/vcs.rst?plain=true" title="View this page"> <svg><use href="#svg-eye"></use></svg> <span class="visually-hidden">View this page</span> </a> </div><div class="edit-this-page"> <a class="muted-link" href="https://github.com/WeblateOrg/weblate/edit/main/docs/vcs.rst" title="Edit this page"> <svg><use href="#svg-pencil"></use></svg> <span class="visually-hidden">Edit this page</span> </a> </div><div class="theme-toggle-container theme-toggle-content"> <button class="theme-toggle"> <div class="visually-hidden">Toggle Light / Dark / Auto color theme</div> <svg class="theme-icon-when-auto-light"><use href="#svg-sun-with-moon"></use></svg> <svg class="theme-icon-when-auto-dark"><use href="#svg-moon-with-sun"></use></svg> <svg class="theme-icon-when-dark"><use href="#svg-moon"></use></svg> <svg class="theme-icon-when-light"><use href="#svg-sun"></use></svg> </button> </div> <label class="toc-overlay-icon toc-content-icon" for="__toc"> <div class="visually-hidden">Toggle table of contents sidebar</div> <i class="icon"><svg><use href="#svg-toc"></use></svg></i> </label> </div> <article role="main" id="furo-main-content"> <section id="version-control-integration"> <span id="vcs"></span><h1>Versjonskontrollintegrasjon<a class="headerlink" href="#version-control-integration" title="Link to this heading">¶</a></h1> <p>Weblate currently supports <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> (with extended support for <a class="reference internal" href="#vcs-github"><span class="std std-ref">GitHub pull requests</span></a>, <a class="reference internal" href="#vcs-gitlab"><span class="std std-ref">GitLab merge requests</span></a>, <a class="reference internal" href="#vcs-gitea"><span class="std std-ref">Gitea pull requests</span></a>, <a class="reference internal" href="#vcs-gerrit"><span class="std std-ref">Gerrit</span></a>, <a class="reference internal" href="#vcs-git-svn"><span class="std std-ref">Subversion</span></a>, <a class="reference internal" href="#vcs-bitbucket-cloud"><span class="std std-ref">Bitbucket Cloud pull requests</span></a>, <a class="reference internal" href="#vcs-bitbucket-data-center"><span class="std std-ref">Bitbucket Data Center pull requests</span></a>, and <a class="reference internal" href="#vcs-azure-devops"><span class="std std-ref">Azure DevOps pull requests</span></a>) and <a class="reference internal" href="#vcs-mercurial"><span class="std std-ref">Mercurial</span></a> as version control back-ends.</p> <section id="accessing-repositories"> <span id="vcs-repos"></span><h2>Accessing repositories<a class="headerlink" href="#accessing-repositories" title="Link to this heading">¶</a></h2> <p>The VCS repository you want to use has to be accessible to Weblate. With a publicly available repository you just need to enter the correct URL (for example <code class="docutils literal notranslate"><span class="pre">https://github.com/WeblateOrg/weblate.git</span></code>), but for private repositories or for push URLs the setup is more complex and requires authentication.</p> <section id="accessing-repositories-from-hosted-weblate"> <span id="hosted-push"></span><h3>Accessing repositories from Hosted Weblate<a class="headerlink" href="#accessing-repositories-from-hosted-weblate" title="Link to this heading">¶</a></h3> <p>For Hosted Weblate, there is a dedicated push user registered on GitHub, Bitbucket, Codeberg, and GitLab (with the username <span class="guilabel">weblate</span>, e-mail <code class="docutils literal notranslate"><span class="pre">hosted@weblate.org</span></code>, and a name or profile description <span class="guilabel">Weblate push user</span>).</p> <div class="admonition hint"> <p class="admonition-title">Hint</p> <p>There can be more Weblate users on the platforms, designated for other Weblate instances. Searching by e-mail <code class="docutils literal notranslate"><span class="pre">hosted@weblate.org</span></code> is recommended to find the correct user for Hosted Weblate.</p> </div> <p>You need to add this user as a collaborator and give it appropriate permissions to your repository (read-only is okay for cloning, write is required for pushing). Depending on the service and your organization’s settings, this happens immediately, or requires confirmation on the Weblate side.</p> <p>The <span class="guilabel">weblate</span> user on GitHub accepts invitations automatically within five minutes. Manual processing might be needed on the other services, so please be patient.</p> <p>Once the <span class="guilabel">weblate</span> user is added to your repository, you can configure <a class="reference internal" href="admin/projects.html#component-repo"><span class="std std-ref">Kodelager for kildekode</span></a> and <a class="reference internal" href="admin/projects.html#component-push"><span class="std std-ref">Dyttingsadresse for kodelager</span></a> using the SSH protocol (for example <code class="docutils literal notranslate"><span class="pre">git@github.com:WeblateOrg/weblate.git</span></code>).</p> </section> <section id="accessing-repositories-on-code-hosting-sites-github-gitlab-bitbucket-azure-devops"> <h3>Accessing repositories on code hosting sites (GitHub, GitLab, Bitbucket, Azure DevOps, …)<a class="headerlink" href="#accessing-repositories-on-code-hosting-sites-github-gitlab-bitbucket-azure-devops" title="Link to this heading">¶</a></h3> <p>Accessing repositories on code hosting sites is typically done by creating a dedicated user who is associated with a Weblate SSH key (see <a class="reference internal" href="#weblate-ssh-key"><span class="std std-ref">Weblate SSH key</span></a>). This way you associate Weblate SSH key with a single user (platforms frequently enforce single use of a SSH key) and grant this user access to the repository. You can then use SSH URL to access the repository (see <a class="reference internal" href="#ssh-repos"><span class="std std-ref">SSH repositories</span></a>).</p> <div class="admonition hint"> <p class="admonition-title">Hint</p> <p>On a Hosted Weblate, this is pre-configured for most of the public sites, please see <a class="reference internal" href="#hosted-push"><span class="std std-ref">Accessing repositories from Hosted Weblate</span></a>.</p> </div> </section> <section id="ssh-repositories"> <span id="ssh-repos"></span><h3>SSH repositories<a class="headerlink" href="#ssh-repositories" title="Link to this heading">¶</a></h3> <p>The most frequently used method to access private repositories is based on SSH. Authorize the public Weblate SSH key (see <a class="reference internal" href="#weblate-ssh-key"><span class="std std-ref">Weblate SSH key</span></a>) to access the upstream repository this way.</p> <div class="admonition warning"> <p class="admonition-title">Advarsel</p> <p>On GitHub, each key can only be used once, see <a class="reference internal" href="#vcs-repos-github"><span class="std std-ref">GitHub repositories</span></a> and <a class="reference internal" href="#hosted-push"><span class="std std-ref">Accessing repositories from Hosted Weblate</span></a>.</p> </div> <p>Weblate also stores the host key fingerprint upon first connection, and fails to connect to the host should it be changed later (see <a class="reference internal" href="#verify-ssh"><span class="std std-ref">Verifying SSH host keys</span></a>).</p> <p>In case adjustment is needed, do so from the Weblate admin interface:</p> <img alt="_images/ssh-keys.webp" src="_images/ssh-keys.webp" /> <section id="weblate-ssh-key"> <span id="id1"></span><h4>Weblate SSH key<a class="headerlink" href="#weblate-ssh-key" title="Link to this heading">¶</a></h4> <div class="versionchanged"> <p><span class="versionmodified changed">Endret i version 4.17: </span>Weblate now generates both RSA and Ed25519 SSH keys. Using Ed25519 is recommended for new setups.</p> </div> <p>The Weblate public key is visible to all users browsing the <span class="guilabel">About</span> page.</p> <p>Admins can generate or display the public key currently used by Weblate in the connection (from <span class="guilabel">SSH keys</span>) on the admin interface landing page.</p> <div class="admonition note"> <p class="admonition-title">Merknad</p> <p>The corresponding private SSH key can not currently have a password, so ensure it is well protected.</p> </div> <div class="admonition hint"> <p class="admonition-title">Hint</p> <p>Make a backup of the generated private Weblate SSH key.</p> </div> </section> <section id="verifying-ssh-host-keys"> <span id="verify-ssh"></span><h4>Verifying SSH host keys<a class="headerlink" href="#verifying-ssh-host-keys" title="Link to this heading">¶</a></h4> <p>Weblate automatically stores the SSH host keys on first access and remembers them for further use.</p> <p>In case you want to verify the key fingerprint before connecting to the repository, add the SSH host keys of the servers you are going to access in <span class="guilabel">Add host key</span>, from the same section of the admin interface. Enter the hostname you are going to access (e.g. <code class="docutils literal notranslate"><span class="pre">gitlab.com</span></code>), and press <span class="guilabel">Submit</span>. Verify its fingerprint matches the server you added.</p> <p>The added keys with fingerprints are shown in the confirmation message:</p> <img alt="_images/ssh-keys-added.webp" src="_images/ssh-keys-added.webp" /> </section> <section id="connecting-to-legacy-ssh-servers"> <h4>Connecting to legacy SSH servers<a class="headerlink" href="#connecting-to-legacy-ssh-servers" title="Link to this heading">¶</a></h4> <p>Recent OpenSSH releases (for example the one used in Weblate Docker container) disable RSA signatures using the SHA-1 hash algorithm by default. This change has been made as the SHA-1 hash algorithm is cryptographically broken, and it is possible to create chosen-prefix hash collisions for <USD$50K.</p> <p>For most users, this change should be invisible and there is no need to replace ssh-rsa keys. OpenSSH has supported RFC8332 RSA/SHA-256/512 signatures since release 7.2 and existing ssh-rsa keys will automatically use the stronger algorithm where possible.</p> <p>Incompatibility is more likely when connecting to older SSH implementations that have not been upgraded or have not closely tracked improvements in the SSH protocol. The SSH connection to such server will fail with:</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>no matching host key type found. Their offer: ssh-rsa </pre></div> </div> <p>For these cases, it may be necessary to selectively re-enable RSA/SHA1 to allow connection and/or user authentication via the HostkeyAlgorithms and PubkeyAcceptedAlgorithms options. For example, the following stanza in <code class="file docutils literal notranslate"><span class="pre">DATA_DIR/ssh/config</span></code> will enable RSA/SHA1 for host and user authentication for a single destination host:</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>Host legacy-host HostkeyAlgorithms +ssh-rsa PubkeyAcceptedAlgorithms +ssh-rsa </pre></div> </div> <p>We recommend enabling RSA/SHA1 only as a stopgap measure until legacy implementations can be upgraded or reconfigured with another key type (such as ECDSA or Ed25519).</p> </section> </section> <section id="github-repositories"> <span id="vcs-repos-github"></span><h3>GitHub repositories<a class="headerlink" href="#github-repositories" title="Link to this heading">¶</a></h3> <p>Access via SSH is possible (see <a class="reference internal" href="#ssh-repos"><span class="std std-ref">SSH repositories</span></a>), but in case you need to access more than one repository, you will hit a GitHub limitation on allowed SSH key usage (since each key can be used only once).</p> <p>In case the <a class="reference internal" href="admin/projects.html#component-push-branch"><span class="std std-ref">Dyttingsforgrening</span></a> is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch.</p> <p>For smaller deployments, use HTTPS authentication with a personal access token and your GitHub account, see <a class="reference external" href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token">Creating an access token for command-line use</a>.</p> <p>For bigger setups, it is usually better to create a dedicated user for Weblate, assign it the public SSH key generated in Weblate (see <a class="reference internal" href="#weblate-ssh-key"><span class="std std-ref">Weblate SSH key</span></a>) and grant it access to all the repositories you want to translate. This approach is also used for Hosted Weblate, there is dedicated <span class="guilabel">weblate</span> user for that.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="#hosted-push"><span class="std std-ref">Accessing repositories from Hosted Weblate</span></a></p> </div> </section> <section id="weblate-internal-urls"> <span id="internal-urls"></span><h3>Weblate internal URLs<a class="headerlink" href="#weblate-internal-urls" title="Link to this heading">¶</a></h3> <p>Share one repository setup between different components by referring to its placement as <code class="docutils literal notranslate"><span class="pre">weblate://project/component</span></code> in other (linked) components. This way linked components use the VCS repository configuration of the main (referenced) component.</p> <div class="admonition warning"> <p class="admonition-title">Advarsel</p> <p>Removing main component also removes linked components.</p> </div> <p>Weblate automatically adjusts the repository URL when creating a component if it finds a component with a matching repository setup. You can override this in the last step of the component configuration.</p> <p>Reasons to use this:</p> <ul class="simple"> <li><p>Saves disk space on the server, the repository is stored just once.</p></li> <li><p>Makes the updates faster, only one repository is updated.</p></li> <li><p>There is just single exported repository with Weblate translations (see <a class="reference internal" href="admin/optionals.html#git-exporter"><span class="std std-ref">Git exporter</span></a>).</p></li> <li><p>Some add-ons can operate on multiple components sharing one repository, for example <a class="reference internal" href="admin/addons.html#addon-weblate-git-squash"><span class="std std-ref">Slå sammen innsjekkinger</span></a>.</p></li> </ul> </section> <section id="https-repositories"> <h3>HTTPS repositories<a class="headerlink" href="#https-repositories" title="Link to this heading">¶</a></h3> <p>To access protected HTTPS repositories, include the username and password in the URL. Don’t worry, Weblate will strip this info when the URL is shown to users (if even allowed to see the repository URL at all).</p> <p>For example the GitHub URL with authentication added might look like: <code class="docutils literal notranslate"><span class="pre">https://user:your_access_token@github.com/WeblateOrg/weblate.git</span></code>.</p> <div class="versionchanged"> <p><span class="versionmodified changed">Endret i version 5.10.2: </span>Weblate uses proactive authentication with Git 2.46.0 and newer when HTTP credentials are supplied.</p> <p>This makes it possible to access Azure DevOps repositories and makes access to authenticated repositories faster.</p> </div> <div class="admonition note"> <p class="admonition-title">Merknad</p> <p>If your username or password contains special characters, those have to be URL encoded, for example <code class="docutils literal notranslate"><span class="pre">https://user%40example.com:%24password%23@bitbucket.org/…</span></code>.</p> </div> </section> <section id="using-proxy"> <h3>Using proxy<a class="headerlink" href="#using-proxy" title="Link to this heading">¶</a></h3> <p>If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it.</p> <p>This can be done using the <code class="docutils literal notranslate"><span class="pre">http_proxy</span></code>, <code class="docutils literal notranslate"><span class="pre">https_proxy</span></code>, and <code class="docutils literal notranslate"><span class="pre">all_proxy</span></code> environment variables, (as described in the <a class="reference external" href="https://curl.se/docs/">cURL documentation</a>) or by enforcing it in the VCS configuration, for example:</p> <div class="highlight-sh notranslate"><div class="highlight"><pre><span></span>git<span class="w"> </span>config<span class="w"> </span>--global<span class="w"> </span>http.proxy<span class="w"> </span>http://user:password@proxy.example.com:80 </pre></div> </div> <div class="admonition note"> <p class="admonition-title">Merknad</p> <p>The proxy configuration needs to be done under user running Weblate (see also <a class="reference internal" href="admin/install.html#file-permissions"><span class="std std-ref">Filsystem-tilganger</span></a>) and with <code class="docutils literal notranslate"><span class="pre">HOME=$DATA_DIR/home</span></code> (see <a class="reference internal" href="admin/config.html#std-setting-DATA_DIR"><code class="xref std std-setting docutils literal notranslate"><span class="pre">DATA_DIR</span></code></a>), otherwise Git executed by Weblate will not use it.</p> </div> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference external" href="https://curl.se/docs/manpage.html">The cURL manpage</a>, <a class="reference external" href="https://git-scm.com/docs/git-config">Git config documentation</a></p> </div> </section> </section> <section id="git"> <span id="vcs-git"></span><h2>Git<a class="headerlink" href="#git" title="Link to this heading">¶</a></h2> <div class="admonition hint"> <p class="admonition-title">Hint</p> <p>Weblate needs Git 2.28 or newer.</p> </div> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p>See <a class="reference internal" href="#vcs-repos"><span class="std std-ref">Accessing repositories</span></a> for info on how to access different kinds of repositories.</p> </div> <section id="git-with-force-push"> <span id="vcs-git-force-push"></span><h3>Git med tvungen dytting<a class="headerlink" href="#git-with-force-push" title="Link to this heading">¶</a></h3> <p>This behaves exactly like Git itself, the only difference being that it always force pushes. This is intended only in the case of using a separate repository for translations.</p> <div class="admonition warning"> <p class="admonition-title">Advarsel</p> <p>Use with caution, as this easily leads to lost commits in your upstream repository.</p> </div> </section> <section id="customizing-git-configuration"> <h3>Customizing Git configuration<a class="headerlink" href="#customizing-git-configuration" title="Link to this heading">¶</a></h3> <p>Weblate invokes all VCS commands with <code class="docutils literal notranslate"><span class="pre">HOME=$DATA_DIR/home</span></code> (see <a class="reference internal" href="admin/config.html#std-setting-DATA_DIR"><code class="xref std std-setting docutils literal notranslate"><span class="pre">DATA_DIR</span></code></a>), therefore editing the user configuration needs to be done in <code class="docutils literal notranslate"><span class="pre">DATA_DIR/home/.git</span></code>.</p> </section> <section id="git-remote-helpers"> <span id="vcs-git-helpers"></span><h3>Git remote helpers<a class="headerlink" href="#git-remote-helpers" title="Link to this heading">¶</a></h3> <p>You can also use Git <a class="reference external" href="https://git-scm.com/docs/gitremote-helpers">remote helpers</a> for additionally supporting other version control systems, but be prepared to debug problems this may lead to.</p> <p>At this time, helpers for Bazaar and Mercurial are available within separate repositories on GitHub: <a class="reference external" href="https://github.com/felipec/git-remote-hg">git-remote-hg</a> and <a class="reference external" href="https://github.com/felipec/git-remote-bzr">git-remote-bzr</a>. Download them manually and put somewhere in your search path (for example <code class="file docutils literal notranslate"><span class="pre">~/bin</span></code>). Make sure you have the corresponding version control systems installed.</p> <p>Once you have these installed, such remotes can be used to specify a repository in Weblate.</p> <p>To clone the <code class="docutils literal notranslate"><span class="pre">gnuhello</span></code> project from Launchpad using Bazaar:</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>bzr::lp:gnuhello </pre></div> </div> <p>For the <code class="docutils literal notranslate"><span class="pre">hello</span></code> repository from selenic.com using Mercurial:</p> <div class="highlight-text notranslate"><div class="highlight"><pre><span></span>hg::https://selenic.com/repo/hello </pre></div> </div> <div class="admonition warning"> <p class="admonition-title">Advarsel</p> <p>The inconvenience of using Git remote helpers is for example with Mercurial, the remote helper sometimes creates a new tip when pushing changes back.</p> </div> </section> </section> <section id="github-pull-requests"> <span id="github-push"></span><span id="vcs-github"></span><h2>GitHub pull requests<a class="headerlink" href="#github-pull-requests" title="Link to this heading">¶</a></h2> <p>This adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://docs.github.com/en/rest">GitHub API</a> to allow pushing translation changes as pull requests, instead of pushing directly to the repository.</p> <p><a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> pushes changes directly to a repository, while <a class="reference internal" href="#vcs-github"><span class="std std-ref">GitHub pull requests</span></a> creates pull requests. The latter is not needed for merely accessing Git repositories.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-GITHUB_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">GITHUB_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">GitHub</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-GITHUB_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">GITHUB_CREDENTIALS</span></code></a></p> </div> </section> <section id="gitlab-merge-requests"> <span id="gitlab-push"></span><span id="vcs-gitlab"></span><h2>GitLab merge requests<a class="headerlink" href="#gitlab-merge-requests" title="Link to this heading">¶</a></h2> <p>This just adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://docs.gitlab.com/ee/api/">GitLab API</a> to allow pushing translation changes as merge requests instead of pushing directly to the repository.</p> <p>There is no need to use this to access Git repositories, ordinary <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> works the same, the only difference is how pushing to a repository is handled. With <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> changes are pushed directly to the repository, while <a class="reference internal" href="#vcs-gitlab"><span class="std std-ref">GitLab merge requests</span></a> creates merge request.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-GITLAB_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">GITLAB_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">GitLab</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-GITLAB_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">GITLAB_CREDENTIALS</span></code></a></p> </div> </section> <section id="gitea-pull-requests"> <span id="gitea-push"></span><span id="vcs-gitea"></span><h2>Gitea pull requests<a class="headerlink" href="#gitea-pull-requests" title="Link to this heading">¶</a></h2> <div class="versionadded"> <p><span class="versionmodified added">Added in version 4.12.</span></p> </div> <p>This just adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://docs.gitea.io/en-us/api-usage/">Gitea API</a> to allow pushing translation changes as pull requests instead of pushing directly to the repository.</p> <p>There is no need to use this to access Git repositories, ordinary <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> works the same, the only difference is how pushing to a repository is handled. With <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> changes are pushed directly to the repository, while <a class="reference internal" href="#vcs-gitea"><span class="std std-ref">Gitea pull requests</span></a> creates pull requests.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-GITEA_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">GITEA_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">Gitea</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-GITEA_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">GITEA_CREDENTIALS</span></code></a></p> </div> </section> <section id="bitbucket-data-center-pull-requests"> <span id="bitbucket-server-push"></span><span id="vcs-bitbucket-data-center"></span><span id="vcs-bitbucket-server"></span><h2>Bitbucket Data Center pull requests<a class="headerlink" href="#bitbucket-data-center-pull-requests" title="Link to this heading">¶</a></h2> <div class="versionadded"> <p><span class="versionmodified added">Added in version 4.16.</span></p> </div> <p>This just adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://developer.atlassian.com/server/bitbucket/">Bitbucket Data Center API</a> to allow pushing translation changes as pull requests instead of pushing directly to the repository.</p> <div class="admonition warning"> <p class="admonition-title">Advarsel</p> <p>This does not support Bitbucket Cloud API.</p> </div> <p>There is no need to use this to access Git repositories, ordinary <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> works the same, the only difference is how pushing to a repository is handled. With <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> changes are pushed directly to the repository, while <a class="reference internal" href="#vcs-bitbucket-data-center"><span class="std std-ref">Bitbucket Data Center pull requests</span></a> creates pull request.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-BITBUCKETSERVER_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">BITBUCKETSERVER_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">Bitbucket Data Center</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-BITBUCKETSERVER_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">BITBUCKETSERVER_CREDENTIALS</span></code></a></p> </div> </section> <section id="bitbucket-cloud-pull-requests"> <span id="bitbucket-cloud-push"></span><span id="vcs-bitbucket-cloud"></span><h2>Bitbucket Cloud pull requests<a class="headerlink" href="#bitbucket-cloud-pull-requests" title="Link to this heading">¶</a></h2> <div class="versionadded"> <p><span class="versionmodified added">Added in version 5.8.</span></p> </div> <p>This just adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://developer.atlassian.com/cloud/bitbucket/">Bitbucket Cloud API</a> to allow pushing translation changes as pull requests instead of pushing directly to the repository.</p> <div class="admonition warning"> <p class="admonition-title">Advarsel</p> <p>This is different from Bitbucket Data Center API.</p> </div> <p>There is no need to use this to access Git repositories, ordinary <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> works the same, the only difference is how pushing to a repository is handled. With <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> changes are pushed directly to the repository, while <a class="reference internal" href="#vcs-bitbucket-cloud"><span class="std std-ref">Bitbucket Cloud pull requests</span></a> creates pull request.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-BITBUCKETCLOUD_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">BITBUCKETCLOUD_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">Bitbucket Cloud</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-BITBUCKETCLOUD_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">BITBUCKETCLOUD_CREDENTIALS</span></code></a></p> </div> </section> <section id="pagure-merge-requests"> <span id="pagure-push"></span><span id="vcs-pagure"></span><h2>Pagure merge requests<a class="headerlink" href="#pagure-merge-requests" title="Link to this heading">¶</a></h2> <div class="versionadded"> <p><span class="versionmodified added">Added in version 4.3.2.</span></p> </div> <p>This just adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://pagure.io/api/0/">Pagure API</a> to allow pushing translation changes as merge requests instead of pushing directly to the repository.</p> <p>There is no need to use this to access Git repositories, ordinary <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> works the same, the only difference is how pushing to a repository is handled. With <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> changes are pushed directly to the repository, while <a class="reference internal" href="#vcs-pagure"><span class="std std-ref">Pagure merge requests</span></a> creates merge request.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-PAGURE_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">PAGURE_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">Pagure</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-PAGURE_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">PAGURE_CREDENTIALS</span></code></a></p> </div> </section> <section id="gerrit"> <span id="vcs-gerrit"></span><h2>Gerrit<a class="headerlink" href="#gerrit" title="Link to this heading">¶</a></h2> <p>Adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://pypi.org/project/git-review/">git-review</a> tool to allow pushing translation changes as Gerrit review requests, instead of pushing them directly to the repository.</p> <p>The Gerrit documentation has the details on the configuration necessary to set up such repositories.</p> </section> <section id="azure-devops-pull-requests"> <span id="azure-devops-push"></span><span id="vcs-azure-devops"></span><h2>Azure DevOps pull requests<a class="headerlink" href="#azure-devops-pull-requests" title="Link to this heading">¶</a></h2> <p>This adds a thin layer atop <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> using the <a class="reference external" href="https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-7.2">Azure DevOps API</a> to allow pushing translation changes as pull requests, instead of pushing directly to the repository.</p> <p><a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a> pushes changes directly to a repository, while <a class="reference internal" href="#vcs-azure-devops"><span class="std std-ref">Azure DevOps pull requests</span></a> creates pull requests. The latter is not needed for merely accessing Git repositories.</p> <p>You need to configure API credentials (<a class="reference internal" href="admin/config.html#std-setting-AZURE_DEVOPS_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">AZURE_DEVOPS_CREDENTIALS</span></code></a>) in the Weblate settings to make this work. Once configured, you will see a <span class="guilabel">Azure DevOps</span> option when selecting <a class="reference internal" href="admin/projects.html#component-vcs"><span class="std std-ref">Versjonskontrollsystem</span></a>.</p> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/continuous.html#push-changes"><span class="std std-ref">Pushing changes from Weblate</span></a>, <a class="reference internal" href="admin/config.html#std-setting-AZURE_DEVOPS_CREDENTIALS"><code class="xref std std-setting docutils literal notranslate"><span class="pre">AZURE_DEVOPS_CREDENTIALS</span></code></a></p> </div> </section> <section id="mercurial"> <span id="vcs-mercurial"></span><h2>Mercurial<a class="headerlink" href="#mercurial" title="Link to this heading">¶</a></h2> <p>Mercurial is another VCS you can use directly in Weblate.</p> <div class="admonition note"> <p class="admonition-title">Merknad</p> <p>It should work with any Mercurial version, but there are sometimes incompatible changes to the command-line interface which breaks Weblate integration.</p> </div> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p>See <a class="reference internal" href="#vcs-repos"><span class="std std-ref">Accessing repositories</span></a> for info on how to access different kinds of repositories.</p> </div> </section> <section id="subversion"> <span id="vcs-git-svn"></span><h2>Subversion<a class="headerlink" href="#subversion" title="Link to this heading">¶</a></h2> <p>Weblate uses <a class="reference external" href="https://git-scm.com/docs/git-svn">git-svn</a> to interact with <a class="reference external" href="https://subversion.apache.org/">subversion</a> repositories. It is a Perl script that lets subversion be used by a Git client, enabling users to maintain a full clone of the internal repository and commit locally.</p> <div class="admonition note"> <p class="admonition-title">Merknad</p> <p>Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be found in the <a class="reference external" href="https://git-scm.com/docs/git-svn#Documentation/git-svn.txt---stdlayout">git-svn documentation</a>. If your repository does not have a standard layout and you encounter errors, try including the branch name in the repository URL and leaving branch empty.</p> </div> <section id="subversion-credentials"> <h3>Subversion credentials<a class="headerlink" href="#subversion-credentials" title="Link to this heading">¶</a></h3> <p>Weblate expects you to have accepted the certificate up-front (and your credentials if needed). It will look to insert them into the <a class="reference internal" href="admin/config.html#std-setting-DATA_DIR"><code class="xref std std-setting docutils literal notranslate"><span class="pre">DATA_DIR</span></code></a> directory. Accept the certificate by using <cite>svn</cite> once with the <cite>$HOME</cite> environment variable set to the <a class="reference internal" href="admin/config.html#std-setting-DATA_DIR"><code class="xref std std-setting docutils literal notranslate"><span class="pre">DATA_DIR</span></code></a>:</p> <div class="highlight-sh notranslate"><div class="highlight"><pre><span></span><span class="c1"># Use DATA_DIR as configured in Weblate settings.py, it is /app/data in the Docker</span> <span class="nv">HOME</span><span class="o">=</span><span class="si">${</span><span class="nv">DATA_DIR</span><span class="si">}</span>/home<span class="w"> </span>svn<span class="w"> </span>co<span class="w"> </span>https://svn.example.com/example </pre></div> </div> <div class="admonition seealso"> <p class="admonition-title">Se også</p> <p><a class="reference internal" href="admin/config.html#std-setting-DATA_DIR"><code class="xref std std-setting docutils literal notranslate"><span class="pre">DATA_DIR</span></code></a></p> </div> </section> </section> <section id="local-files"> <span id="vcs-local"></span><h2>Local files<a class="headerlink" href="#local-files" title="Link to this heading">¶</a></h2> <div class="admonition hint"> <p class="admonition-title">Hint</p> <p>Underneath, this uses <a class="reference internal" href="#vcs-git"><span class="std std-ref">Git</span></a>. It requires Git installed and allows you to switch to using Git natively with full history of your translations.</p> </div> <p>Weblate can also operate without a remote VCS. The initial translations are imported by uploading them. Later you can replace individual files by file upload, or add translation strings directly from Weblate (currently available only for monolingual translations).</p> <p>In the background Weblate creates a Git repository for you and all changes are tracked in. In case you later decide to use a VCS to store the translations, you already have a repository within Weblate can base your integration on.</p> </section> </section> </article> </div> <footer> <div class="related-pages"> <a class="next-page" href="api.html"> <div class="page-info"> <div class="context"> <span>Next</span> </div> <div class="title">Weblate’s REST API</div> </div> <svg class="furo-related-icon"><use href="#svg-arrow-right"></use></svg> </a> <a class="prev-page" href="faq.html"> <svg class="furo-related-icon"><use href="#svg-arrow-right"></use></svg> <div class="page-info"> <div class="context"> <span>Previous</span> </div> <div class="title">Frequently Asked Questions</div> </div> </a> </div> <div class="bottom-of-page"> <div class="left-details"> <div class="copyright"> Copyright © Michal Čihař </div> Made with <a href="https://www.sphinx-doc.org/">Sphinx</a> and <a class="muted-link" href="https://pradyunsg.me">@pradyunsg</a>'s <a href="https://github.com/pradyunsg/furo">Furo</a> </div> <div class="right-details"> <div class="icons"> </div> </div> </div> </footer> </div> <aside class="toc-drawer"> <div class="toc-sticky toc-scroll"> <div class="toc-title-container"> <span class="toc-title"> On this page </span> </div> <div class="toc-tree-container"> <div class="toc-tree"> <ul> <li><a class="reference internal" href="#">Versjonskontrollintegrasjon</a><ul> <li><a class="reference internal" href="#accessing-repositories">Accessing repositories</a><ul> <li><a class="reference internal" href="#accessing-repositories-from-hosted-weblate">Accessing repositories from Hosted Weblate</a></li> <li><a class="reference internal" href="#accessing-repositories-on-code-hosting-sites-github-gitlab-bitbucket-azure-devops">Accessing repositories on code hosting sites (GitHub, GitLab, Bitbucket, Azure DevOps, …)</a></li> <li><a class="reference internal" href="#ssh-repositories">SSH repositories</a><ul> <li><a class="reference internal" href="#weblate-ssh-key">Weblate SSH key</a></li> <li><a class="reference internal" href="#verifying-ssh-host-keys">Verifying SSH host keys</a></li> <li><a class="reference internal" href="#connecting-to-legacy-ssh-servers">Connecting to legacy SSH servers</a></li> </ul> </li> <li><a class="reference internal" href="#github-repositories">GitHub repositories</a></li> <li><a class="reference internal" href="#weblate-internal-urls">Weblate internal URLs</a></li> <li><a class="reference internal" href="#https-repositories">HTTPS repositories</a></li> <li><a class="reference internal" href="#using-proxy">Using proxy</a></li> </ul> </li> <li><a class="reference internal" href="#git">Git</a><ul> <li><a class="reference internal" href="#git-with-force-push">Git med tvungen dytting</a></li> <li><a class="reference internal" href="#customizing-git-configuration">Customizing Git configuration</a></li> <li><a class="reference internal" href="#git-remote-helpers">Git remote helpers</a></li> </ul> </li> <li><a class="reference internal" href="#github-pull-requests">GitHub pull requests</a></li> <li><a class="reference internal" href="#gitlab-merge-requests">GitLab merge requests</a></li> <li><a class="reference internal" href="#gitea-pull-requests">Gitea pull requests</a></li> <li><a class="reference internal" href="#bitbucket-data-center-pull-requests">Bitbucket Data Center pull requests</a></li> <li><a class="reference internal" href="#bitbucket-cloud-pull-requests">Bitbucket Cloud pull requests</a></li> <li><a class="reference internal" href="#pagure-merge-requests">Pagure merge requests</a></li> <li><a class="reference internal" href="#gerrit">Gerrit</a></li> <li><a class="reference internal" href="#azure-devops-pull-requests">Azure DevOps pull requests</a></li> <li><a class="reference internal" href="#mercurial">Mercurial</a></li> <li><a class="reference internal" href="#subversion">Subversion</a><ul> <li><a class="reference internal" href="#subversion-credentials">Subversion credentials</a></li> </ul> </li> <li><a class="reference internal" href="#local-files">Local files</a></li> </ul> </li> </ul> </div> </div> </div> </aside> </div> </div><script src="_static/documentation_options.js?v=8984a097"></script> <script src="_static/doctools.js?v=9bcbadda"></script> <script src="_static/sphinx_highlight.js?v=dc90522c"></script> <script src="_static/scripts/furo.js?v=5fa4622c"></script> <script src="_static/clipboard.min.js?v=a7894cd8"></script> <script src="_static/copybutton.js?v=f281be69"></script> </body> </html>