🐛 add check for empty github workflow uses
          #4832
        
          
      
                
     Open
            
            
          
  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.
  
    
  
    
What kind of change does this PR introduce?
bug fix
What is the current behavior?
The Pinned-Dependency check is dereferencing nil pointers on repos which use GitHub's new YAML anchor syntax in their workflows.
https://github.blog/changelog/2025-09-18-actions-yaml-anchors-and-non-public-workflow-templates/
What is the new behavior (if this is a feature change)?**
Ignore cases where the
usesfield isn't set. The value isn't actually empty in the testcase which triggered the panic, but our GitHub workflow library doesn't currently support parsing GitHub's new YAML anchors/aliases.Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note(In particular, describe what changes users might need to make in their
application as a result of this pull request.)