ci: disable Snap Build and Snap Store publish#175
Merged
Conversation
Hard-disable the publish-snap job by setting `if: false`. The original condition is preserved in a comment so the job can be re-enabled with a one-line change when Snap Store publication resumes.
Hard-disable the snap-build job in CI by setting `if: false`. The original condition is preserved in a comment so the job can be re-enabled with a one-line change once Snap packaging resumes.
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
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.
Summary
publish-snapjob in.github/workflows/release.ymlby settingif: false.snap-buildjob in.github/workflows/ci.ymlthe same way.snap/snapcraft.yaml,snap-build-inputs, and thepublish_snapworkflow_dispatch input all remain in place.Test plan
skipping.Publish Snapjob appears as skipped (not pending or running).