release: remove pmc deployment workflow #587
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ldennington
force-pushed
the
remove-apt-deployment
branch
from
8333c49 to
71be135
Compare
The Debian package for each microsoft/git release is currently deployed to packages.microsoft.com. The team that manages this feed is migrating to a new "vNext Publishing API" [1]. Because the new API has several administrative pre-requisites and the maintainers believe consumption of microsoft/git from this feed to be negligible, the decision was made to cease deploying to packages.microsoft.com rather than migrate to the new API. This change removes the workflow that handled this deployment. 1: https://microsoft.sharepoint.com/teams/PMC/SitePages/API-An.aspx
ldennington
force-pushed
the
remove-apt-deployment
branch
from
71be135 to
e8f9030
Compare
vdye
pushed a commit
that referenced
this pull request
Jul 19, 2023
The Debian package for each microsoft/git release is currently deployed to packages.microsoft.com. The team that manages this feed is migrating to a new "vNext Publishing API" [1]. Because the new API has several administrative pre-requisites and the maintainers believe consumption of microsoft/git from this feed to be negligible, the decision was made to cease deploying to packages.microsoft.com rather than migrate to the new API. This change removes the workflow that handled this deployment. 1: https://microsoft.sharepoint.com/teams/PMC/SitePages/API-An.aspx
dscho
pushed a commit
that referenced
this pull request
Aug 8, 2023
The Debian package for each microsoft/git release is currently deployed to packages.microsoft.com. The team that manages this feed is migrating to a new "vNext Publishing API" [1]. Because the new API has several administrative pre-requisites and the maintainers believe consumption of microsoft/git from this feed to be negligible, the decision was made to cease deploying to packages.microsoft.com rather than migrate to the new API. This change removes the workflow that handled this deployment. 1: https://microsoft.sharepoint.com/teams/PMC/SitePages/API-An.aspx
dscho
pushed a commit
that referenced
this pull request
Aug 8, 2023
The Debian package for each microsoft/git release is currently deployed to packages.microsoft.com. The team that manages this feed is migrating to a new "vNext Publishing API" [1]. Because the new API has several administrative pre-requisites and the maintainers believe consumption of microsoft/git from this feed to be negligible, the decision was made to cease deploying to packages.microsoft.com rather than migrate to the new API. This change removes the workflow that handled this deployment. 1: https://microsoft.sharepoint.com/teams/PMC/SitePages/API-An.aspx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Debian package for each microsoft/git release is currently deployed to packages.microsoft.com. The team that manages this feed is migrating to a new "vNext Publishing API" [1]. Because the new API has several administrative pre-requisites and the maintainers believe consumption of microsoft/git from this feed to be negligible, the decision was made to cease deploying to packages.microsoft.com rather than migrate to the new API. This change removes the workflow that handled this deployment.
1: https://microsoft.sharepoint.com/teams/PMC/SitePages/API-An.aspx