well as build the manual locally to check for errors. (You need to do this step only once). # for ssh access git clone git@invent.kde.org:/docs-krita-org.git git remote add upstream git@invent -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent

이 방식의 장점은 컴퓨터에서 사용하던 도구로 텍스트 파일을 편집하고 로컬에서 직접 설명서를 빌드해서 오류를 검사할 수 있습니다. (이 단계는 한 번만 수행하면 됩니다.) # SSH 접근 git clone git@invent.kde.org:<사용자_이름>/docs-krita-org.git git remote add upstream git@invent.kde -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent

URL 将改动 push 回你的 fork。此⽅式的优点是你可以使⽤本机的任意⼯具来编 辑这些源⽂件，也可以在本机⼿动构建 Krita ⽂档项⽬来检查 错误。(你只需执⾏本步骤⼀次)。 # 通过 SSH 访问 git clone git@invent.kde.org�/docs-krita-org.git git remote add upstream git@invent -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org�/krita.git # for https access git clone https://invent

URL 将改动 push 回你的 fork。此方式的优点 是你可以使用本机的任意工具来编辑这些源文件，也可以在本机手动构建 Krita 文档项目来检查错误。(你只需执行本步骤一次)。 # 通过 SSH 访问 git clone git@invent.kde.org:/docs-krita-org.git git remote add upstream git@invent.kde -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent

将改动 push 回你的 fork。此方式的优点 是你可以使用本地系统中的任意工具来编辑这些源文件，也可以在本地手 动构建 Krita 文档项目来检查错误。(你只需执行本步骤一次)。 # 通过 SSH 访问 git clone git@invent.kde.org:/docs-krita-org.git git remote add upstream git@invent.kde -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent

将改动 push 回你的 fork。此方式的优点是你可以使用本地系统中的任意工 具来编辑这些源文件，也可以在本地手动构建 Krita 文档项目 来检查错误。(你只需执行本步骤一次)。 # 通过 SSH 访问 git clone git@invent.kde.org�/docs-krita-org.git git remote add upstream git@invent.kde -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org�/krita.git # for https access git clone https:��invent

将改动 push 回你的 fork。此方式的优点 是你可以使用本地系统中的任意工具来编辑这些源文件，也可以在本地手 动构建 Krita 文档项目来检查错误。(你只需执行本步骤一次)。 # 通过 SSH 访问 git clone git@invent.kde.org:/docs-krita-org.git git remote add upstream git@invent.kde -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent

将改动 push 回你的 fork。此方式的优点 是你可以使用本地系统中的任意工具来编辑这些源文件，也可以在本地手 动构建 Krita 文档项目来检查错误。(你只需执行本步骤一次)。 # 通过 SSH 访问 git clone git@invent.kde.org:/docs-krita-org.git git remote add upstream git@invent.kde -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent

の方法の利点は、コンピュータ上のすべてのツールを使用してこれらの ファイルを編集したり、エラーをチェックするためのマニュアルを ローカル上に作成したりできることです(この手順は最初の1回だけ実行 します)。 # SSH 接続用 git clone git@invent.kde.org:<ユーザ名>/docs-krita-org.git git remote add upstream git@invent.kde. -and-gitlab], but it is slightly different. To push to invent.kde.org, you will not need to have SSH access setup, but you do KDE identity account. If several of your merge requests are accepted, you the git urls to do the git clone from. You can then pull and push your commits from these. # for ssh access git clone git@invent.kde.org:/krita.git # for https access git clone https://invent