Handle private repos in workflow migration#548
Merged
llucax merged 1 commit intofrequenz-floss:v0.x.xfrom Mar 30, 2026
Merged
Conversation
Contributor
Author
|
Skip release notes because this fixes/improves an unreleased migration script. |
ace7c0f to
5736687
Compare
Treat the docs and PyPI publish patterns in ci.yaml as optional when the repository appears to be private, so migrations do not fail just because those jobs were removed intentionally. When those publish jobs are still present in a private repository, warn with a manual step so maintainers can remove them after applying the workflow updates. Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
5736687 to
f50a702
Compare
Marenz
approved these changes
Mar 30, 2026
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
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.
Treat the docs and PyPI publish patterns in ci.yaml as optional when the repository appears to be private, so migrations do not fail just because those jobs were removed intentionally.
When those publish jobs are still present in a private repository, warn with a manual step so maintainers can remove them after applying the workflow updates.