Pro Git 2nd Edition 2.1.413
to have a human- readable name to go with a commit, you can run git describe on that commit. In response, Git generates a string consisting of the name of the most recent tag earlier than that commit when it was delivered, if it was successful and the body and headers for both the request and the response. This makes it incredibly easy to test and debug your hooks. Figure 132. Web hook debugging information credentials for the given properties from this helper’s memory. For the store and erase actions, no response is required (Git ignores it anyway). For the get action, however, Git is very interested in what0 码力 | 731 页 | 21.49 MB | 1 年前3Pro Git 2nd Edition 2.1.413
to have a human-readable name to go with a commit, you can run git describe on that commit. In response, Git generates a string consisting of the name of the most recent tag earlier than that commit when it was delivered, if it was successful and the body and headers for both the request and the response. This makes it incredibly easy to test and debug your hooks. 211 Figure 132. Web hook debugging credentials for the given properties from this helper’s memory. For the store and erase actions, no response is required (Git ignores it anyway). For the get action, however, Git is very interested in what0 码力 | 501 页 | 17.96 MB | 1 年前3Pro Git 2nd Edition 2.1.413
to have a human- readable name to go with a commit, you can run git describe on that commit. In response, Git generates a string consisting of the name of the most recent tag earlier than that commit when it was delivered, if it was successful and the body and headers for both the request and the response. This makes it incredibly easy to test and debug your hooks. Figure 132. Web hook debugging information credentials for the given properties from this helper’s memory. For the store and erase actions, no response is required (Git ignores it anyway). For the get action, however, Git is very interested in what0 码力 | 691 页 | 13.35 MB | 1 年前3Gitea v1.21.1 中文文档
bearer_token_file 中使用。 ENABLE_SWAGGER : true: 是否启用swagger路由 ( /api/swagger , /api/v1/swagger , …)。 MAX_RESPONSE_ITEMS : 50: 单个页面的最大 Feed. ENABLE_OPENID_SIGNIN : false: 允许使用OpenID登录,当设置为 true 时可以通过 /user/login Gitea。 提交 PR 玩转 Gitea - 274 - 本文档使用 书栈网 · BookStack.CN 构建 通常情况下, ENABLE_SWAGGER 默认开启并且参数 MAX_RESPONSE_ITEMS 默认为 50。您可以从 Config Cheat Sheet 中获取更多配置相关信息。 Gitea 支持以下几种 API 认证方式: HTTP basic authentication https://[YOUR-GITEA-URL]/login/oauth/authorize?client_id=CLIENT_ID&redirect_uri=REDIRECT_URI& response_type=code&state=STATE 在设置中注册应用程序以获得 CLIENT_ID 。 STATE 是一个随机字符串,它将在获得用户授权后发送回您的 客户端类型 示例0 码力 | 303 页 | 3.88 MB | 1 年前3
共 4 条
- 1