push credentials on github actions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
👋 Hey!
First, thank you for this wonderful project.
I'm writing here because I'm trying to write a git extension called git-metrics which would allow to store metrics regarding the project, inside git notes, with a simple CLI, so that we don't need to rely on external services.
I have some commands working (add, remove, show) but when it comes to push and pull, it becomes a bit more tricky considering it involves some authentication.
In this PR, I'm trying to use git-metrics push to push my notes, directly from a github action. Using git, we just need to do git push origin refs/notes/metrics and the authentication works out of the box.
With git2, the authentication doesn't seem to work.
Does anyone know, what is the proper way to authenticate using git2 on github actions?
Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the git-metrics push command in the linked PR and trace how it invokes git2 authentication within GitHub Actions. The issue names no repository files or tests; done means establishing a supported authentication path or clearly documenting that path for pushing git notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, rust
- Domain
- authentication, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100