Skip to content
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

fix(templates): handle nil PrivateGitHub #1034

Merged
merged 1 commit into from
Jan 5, 2024

Conversation

ecrupper
Copy link
Contributor

@ecrupper ecrupper commented Jan 5, 2024

A nil check that primarily impacts CLI use, as the chances of this happening during normal pipeline expansion within the Vela server is pretty much 0%.

However, if a user doesn't supply git credentials and tries to validate a pipeline with a remote template, this prevents a seg fault.

@ecrupper ecrupper requested a review from a team as a code owner January 5, 2024 19:58
Copy link

codecov bot commented Jan 5, 2024

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (4906635) 67.00% compared to head (ae698e6) 67.01%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1034      +/-   ##
==========================================
+ Coverage   67.00%   67.01%   +0.01%     
==========================================
  Files         330      330              
  Lines       14075    14080       +5     
==========================================
+ Hits         9431     9436       +5     
  Misses       4165     4165              
  Partials      479      479              
Files Coverage Δ
compiler/native/expand.go 68.04% <57.14%> (+0.67%) ⬆️

@ecrupper ecrupper merged commit de5cf10 into main Jan 5, 2024
10 of 12 checks passed
@ecrupper ecrupper deleted the fix/template/handle-privgit-nil branch January 5, 2024 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants