首页 文库资料 文章资讯  上传文档  发布文章  登录账户

分类

全部综合其他(127)Weblate(127)数据库(12)TiDB(12)后端开发(1)Go(1)

语言

全部英语(140)

格式

全部PDF文档 PDF(76)其他文档 其他(64)
 
本次搜索耗时 0.140 秒，为您找到相关结果约 140 个.

  • epub文档 The Weblate Manual 4.15.1

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 803 页 | 11.20 MB | 1 年前
    3

  • epub文档 The Weblate Manual 4.15.2

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 803 页 | 11.20 MB | 1 年前
    3

  • epub文档 The Weblate Manual 4.15

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 807 页 | 11.20 MB | 1 年前
    3

  • pdf文档 The Weblate Manual 4.15.1

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 509 页 | 7.40 MB | 1 年前
    3

  • pdf文档 The Weblate Manual 4.15.2

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 509 页 | 7.40 MB | 1 年前
    3

  • pdf文档 The Weblate Manual 4.15

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 511 页 | 7.36 MB | 1 年前
    3

  • epub文档 The Weblate Manual 4.14.2

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 806 页 | 11.17 MB | 1 年前
    3

  • pdf文档 The Weblate Manual 4.14.2

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 508 页 | 7.30 MB | 1 年前
    3

  • epub文档 The Weblate Manual 4.16.2

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control changes from Weblate, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 807 页 | 11.23 MB | 1 年前
    3

  • epub文档 The Weblate Manual 4.16

    Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control changes from Weblate, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when
    0 码力 | 807 页 | 11.23 MB | 1 年前
    3
共 140 条
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 14
前往
页
相关搜索词
TheWeblateManual4.154.144.16