microsoft / microsoft/winget-create
Azure Pipeline task for WingetDistribute
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 651
- Forks
- 114
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 3
Description
I'm not sure if this is the right area for this at all, so please move it if this is not where it belongs.
Description of the new feature/enhancement
As a publisher, I would like my own Azure Pipeline to be able to automatically submit packages to the community repo.
Proposed technical implementation details (optional)
Add a task to azure pipelines that would allow publishers with their own CI/CD pipelines to be able to submit package manifests through their release pipeline
Slightly related to microsoft/winget-pkgs#1515
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
The issue names no files or tests. Start by reviewing the Azure Pipelines task request and the related microsoft/winget-pkgs#1515 issue, then identify the existing submission entry points and the pipeline interface involved. Done means publishers can submit package manifests from their own Azure Pipelines, with documented behavior and coverage for the task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100