Gmsh: Use GitHub release assets - #164
Open
kopperp wants to merge 2 commits into
Open
Conversation
kopperp
force-pushed
the
gmsh.github.assets
branch
from
August 30, 2026 10:02
c8275bc to
60ca990
Compare
☂️ Code Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
kopperp
force-pushed
the
gmsh.github.assets
branch
from
August 30, 2026 10:11
60ca990 to
abc900f
Compare
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
1 participant
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.
Self-hosted Gitlab mirrors do not meet our reliability requirements for the distribution of the Gmsh Python wheels. Hosting the Gmsh Python wheels as GitHub release assets ensures they do not count against our GitHub LFS budget but are readily available to all users.