- 
                Notifications
    
You must be signed in to change notification settings  - Fork 20
 
Avoid listing org packages where job token doesn't have access #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
14e6a9b    to
    e3b8a29      
    Compare
  
    | 
           @chizkiyahu friendly ping  | 
    
| 
           @mering  | 
    
ad8b5cc    to
    ef95667      
    Compare
  
    | 
           Latest version has been tested in my fork and all tests pass. Prefer   | 
    
| 
           Oh, I see that the maximum permissions for pull   | 
    
1906219    to
    4dad56d      
    Compare
  
    | 
           This should be working now also for the PR workflow.  | 
    
It's possible if you set permissions packages:write and specify the image name explicitly
983bedd    to
    a0c1a60      
    Compare
  
    | 
           Running workflows from forks seems difficult. I updated the user name to match the one from PAT.  | 
    
| 
           @mering  | 
    
a0c1a60    to
    7e01744      
    Compare
  
    | 
           I checked and access to secrets isn't possible for pull requests from public forks.... I guess the problem is that a package does not have the   | 
    
| 
           @mering  | 
    
Follow-up on #23 but now including a fix to taking the special case into account where
package_namedoesn't exist.Unfortunately, I can't run the tests as I don't have access to create the packages for testing (403 permission denied).
This allows using the job token directly.
Example workflow: