fix(ci): repair invalid refresh-vuln-db workflow (duplicate env key) - #265
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Mengapa
refresh-vuln-db.ymlgagal 0 detik di SETIAP push (254 run gagal,event: push) padahalon:-nya cumaschedule+workflow_dispatch.gh run viewmengonfirmasi: "This run likely failed because of a workflow file issue" — nama run muncul sebagai path file, bukanname:field → GitHub gagal meng-compile.Root cause: step "Push branch + create PR" punya dua key
env:(satuGH_TOKEN, satu blok display vars). PyYAML diam-diam ambil yang terakhir (jadiyaml.safe_loadlolos), tapi parser GitHub Actions menolak duplicate mapping key → file invalid → run gagal di tiap push.Bonus: step "Create branch + commit" punya blok
env:yang ke-indent 10 spasi sehingga ketelan ke dalamrun: |(var commit message jadi kosong).Perbaikan
env:di "Push branch + create PR" jadi satu (GH_TOKEN + 5 display vars).env:"Create branch + commit" ke step-level (8 spasi) sebelumrun:.Verifikasi
Recursive duplicate-key check + schema parse: OK, no duplicate keys. Kedua step sekarang punya
envproper (dikonfirmasi viayaml.safe_load).Setelah merge: workflow file valid → tidak ada lagi push-noise; schedule bulanan + dispatch berfungsi.