feat: add 3 new error entries (concurrency-timing x1, triggers x1, yaml-syntax x1)#412
Merged
Conversation
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.
New Error Entries — Strategy 6 Round 254 (Category Gap Fill)
Targeting the 3 categories with fewest entries: concurrency-timing (104), triggers (116), yaml-syntax (116).
ct-104 — Branch-Scoped Concurrency Group Allows Simultaneous Deployments to Same Environment
errors/concurrency-timing/environment-deployment-branch-scoped-concurrency-cross-branch-collision.ymlgithub.ref/github.ref_namecreate separate slots per branch. Two branches deploying to the same environment have different groups and run simultaneously, causing deployment races. Fix: usejob.environmentas the concurrency key.tr-118 —
workflow_runrequestedType Fires Before Upstream Executeserrors/triggers/workflow-run-requested-type-fires-before-upstream-executes.ymlrequestedactivity type fires when the upstream workflow is queued, before any steps run. Artifacts, outputs, and conclusion are unavailable. Also fires unnecessarily when the upstream run is later cancelled. Only appropriate for pure notification/audit workflows.ys-120 —
startsWith(),endsWith(),contains()Are Case-Insensitiveerrors/yaml-syntax/startswith-endswith-contains-case-insensitive-expression.yml==for exact case-sensitive matching, ortoLower()to document intent explicitly.