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.
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.
build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch
build · deepseek-v4-pro
[0m⚙ [0mexecute {"code":"const res = await tools.read({ path: "/workspace/CV_Website/CV_Site_Nuxt/.pr-review-diff.patch", limit: 2000 }); return res;"}
[0m→ [0mRead .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
[0m
> build · deepseek-v4-pro
[0m→ [0mRead .pr-review-diff.patch
> build · deepseek-v4-pro
[0m⚙ [0mexecute {"code":"const res = await tools.read({ path: \"/workspace/CV_Website/CV_Site_Nuxt/.pr-review-diff.patch\", limit: 2000 }); return res;"}
[0m→ [0mRead .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 main2026-10-18 18:53:54 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
[0m
[NIT] .gitea/workflows/release-please.yml:33 - hardcodes the personal account name
Noelasgit-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