fix(ci): give release-please git credentials for the release-branch push #9

Merged
Noel merged 1 commits from fix/release-please-git-credentials into main 2026-10-18 18:53:54 +00:00
Owner

The 401 in run 89 was the final isomorphic-git push inside
code-suggester's createPullRequest, not an API call: tree, commit and
local ref update all ran through the token-authenticated octokit API,
then 'git push' used the git-username/git-password inputs - unset in
our workflow, so the push was anonymous. The remote branch
release-please--branches--main still sat at an old commit, proving the
push never landed. Pass the account name and the same token.

The 401 in run 89 was the final isomorphic-git push inside code-suggester's createPullRequest, not an API call: tree, commit and local ref update all ran through the token-authenticated octokit API, then 'git push' used the git-username/git-password inputs - unset in our workflow, so the push was anonymous. The remote branch release-please--branches--main still sat at an old commit, proving the push never landed. Pass the account name and the same token.
Noel added 1 commit 2026-10-18 18:51:38 +00:00
fix(ci): give release-please git credentials for the release-branch push
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 35s
PR Check / Typecheck (pull_request) Successful in 38s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / Dependency audit (pull_request) Failing after 9s
PR Check / Dockerfile lint (droast) (pull_request) Failing after 4s
PR Check / AI code review (opencode) (pull_request) Successful in 28s
a27bbbb2ab
The 401 in run 89 was the final isomorphic-git push inside
code-suggester's createPullRequest, not an API call: tree, commit and
local ref update all ran through the token-authenticated octokit API,
then 'git push' used the git-username/git-password inputs - unset in
our workflow, so the push was anonymous. The remote branch
release-please--branches--main still sat at an old commit, proving the
push never landed. Pass the account name and the same token.
Author
Owner



build · deepseek-v4-pro
→ Read .pr-review-diff.patch
build · deepseek-v4-pro
⚙ execute {"code":"const res = await tools.read({ path: "/workspace/CV_Website/CV_Site_Nuxt/.pr-review-diff.patch", limit: 2000 }); return res;"}
→ Read .gitea/workflows/release-please.yml
build · deepseek-v4-pro
The diff contains only CI workflow config (.gitea/workflows/release-please.yml, Gitea Actions YAML) — no application code (Nuxt/Vue/TS/Go) to review.

[NIT] .gitea/workflows/release-please.yml:33 - hardcodes the personal account name Noel as git-username; pushes and attribution break if the account is renamed or the workflow is reused elsewhere. Prefer a bot/service account name kept alongside the token in a secret or repo variable.

VERDICT: APPROVE

 > build · deepseek-v4-pro → Read .pr-review-diff.patch > build · deepseek-v4-pro ⚙ execute {"code":"const res = await tools.read({ path: \"/workspace/CV_Website/CV_Site_Nuxt/.pr-review-diff.patch\", limit: 2000 }); return res;"} → Read .gitea/workflows/release-please.yml > build · deepseek-v4-pro The diff contains only CI workflow config (`.gitea/workflows/release-please.yml`, Gitea Actions YAML) — no application code (Nuxt/Vue/TS/Go) to review. [NIT] .gitea/workflows/release-please.yml:33 - hardcodes the personal account name `Noel` as `git-username`; pushes and attribution break if the account is renamed or the workflow is reused elsewhere. Prefer a bot/service account name kept alongside the token in a secret or repo variable. VERDICT: APPROVE
Noel merged commit 0e5ddda59d into main 2026-10-18 18:53:54 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: CV_Website/CV_Site_Nuxt#9