-
Notifications
You must be signed in to change notification settings - Fork 6
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
Private repositories can not be handled, missing auth #43
Comments
@Xerkus Would you try the improvement/use_github_api_for_all_access branch and see if things work as you expect? |
Lineage configuration is found, but it fails at cloning the repo. |
Ahh, sorry. I made a poor assumption about cloning behavior so I apologize. I have made a composition branch for testing because the two changes needed to resolve your issues belong in their own PRs. Would you try the testing/private_repo_access branch and let me know if things work as you expect this time? |
Yes, this issue is resolved in the The error that I see now is #44 when trying to fetch the upstream:
action-lineage/src/lineage/entrypoint.py Line 455 in 68d1458
|
🐛 Summary
Private repositories can not be processed due to check for lineage configuration never returning result from unauthenticated request:
action-lineage/src/lineage/entrypoint.py
Lines 110 to 118 in 3a0be21
To reproduce
Steps to reproduce the behavior:
Expected behavior
Lineage action can get past the check for lineage configuration existence
Any helpful log output or screenshots
The text was updated successfully, but these errors were encountered: