git-ecosystem / git-ecosystem/git-credential-manager
Republish deb packages to MSFT Ubuntu, Debian, etc. feeds
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Feature description
https://github.com/git-ecosystem/git-credential-manager/pull/516 and related seems to have removed publishing .deb releases to MSFT apt lists for things like Ubuntu, Debian, etc.
Without this, one cannot simply do apt install git-credential-manager for instance (e.g., after adding the appropriate sources).
As that is the preferred mode of install for several use cases (e.g., to avoid bloated and unnecessary dotnet dependencies), this leaves users with hand rolled scripts to install an unsigned package that has no "latest" version or regular updates.
This can lead to security concerns of its own in addition to any it is trying to mitigate by, for instance, acting as a replacement for ssh authentication.
Please consider adding support for this standard installation method back into the mix.
Thanks!
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 by reviewing pull request #516 and the release configuration responsible for publishing .deb packages to MSFT apt feeds. Confirm the Ubuntu and Debian feeds receive current packages and that apt install git-credential-manager works through the documented sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, ubuntu
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100