You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by zh...@apache.org on 2026/08/02 04:49:24 UTC

(shardingsphere) branch master updated: Add token-first GitHub API access guidance (#39311)

This is an automated email from the ASF dual-hosted git repository.

terrymanu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new 6f4173cb278 Add token-first GitHub API access guidance (#39311)
6f4173cb278 is described below

commit 6f4173cb2782a63040ff8cbd23ee1e8d08671996
Author: Liang Zhang <zh...@apache.org>
AuthorDate: Sun Aug 2 12:49:17 2026 +0800

    Add token-first GitHub API access guidance (#39311)
---
 AGENTS.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 2916643295b..9d6a638871b 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -112,6 +112,11 @@ message is not authorization to commit.
   repository, deployment, production API, connector, cloud task, message, or
   other remote state. Perform a remote write only when the current request
   explicitly names the action and exact target.
+- For GitHub access, use the first configured token in this order: `GH_TOKEN`,
+  then `GITHUB_TOKEN`; check it without printing, logging, persisting, or
+  otherwise exposing its value. When a token is available, call the GitHub API
+  directly and do not search for, inspect, or invoke `gh`; use `gh` only when
+  neither token is configured.
 - Do not transmit credentials, tokens, private keys, private logs, proprietary
   source, personal data, connection strings, or other sensitive repository data
   outside the active user-authorized Codex task, including to websites, search