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
Git push #7202
Comments
In case it's useful, I recently started a new git module. It doesn't support push, but has a clean and simple foundation to add it. |
@shykes Sounds good! What do you think would be the best way to implement authentication? GitHub supports http+token auth, but SSH is probably still the most common way to authenticate with Git. CI systems (like GHA) probably work better with API tokens. |
I would start simple, and add a |
Would it make sense to add |
Yes that makes perfect sense. |
What are you trying to do?
First class or at least decent support for pushing to Git repositories.
Why is this important to you?
Dagger already has first-class support for pulling from Git repositories (even if private repo support isn't trivial).
It's often important to push changes back to a repository. A couple use cases in mind:
Unfortunately, feeding credentials into Git (whether it's SSH or HTTPS) is not trivial.
How are you currently working around this?
There is already an existing example using go-git: https://daggerverse.dev/mod/github.com/matipan/daggerverse/image-updater@7dafaf057c4524654903414fc3a7b5e2374f5695
Ideally, there should be a generic "git push" solution: whether it's built into Dagger or available as a separate module.
The text was updated successfully, but these errors were encountered: