Auto build a dev release with Github Actions#44
Open
bjesus wants to merge 1 commit intoosnr:masterfrom
Open
Conversation
Owner
|
Hmm. This is good work, but I'm not sure I actually want to make it easier to install just yet (especially if it's at the cost of making the extension a sealed artifact that people can't modify). Will leave this open and think about it. |
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.
Hi! I'm not sure if this is something you're interested in, but I thought it could help other try out TabFS faster.
This PR doesn't change any TabFS code. Instead it just adds a GH Action workflow that compiles the filesystem (for Linux only at this point, as I couldn't test it on a mac), and packs the extension using Mozilla's Web-ext. It then creates a "pre-release" holding the two assets - a tar file the one can just untar and run "install.sh", and a zip file the one can load onto Firefox Developer Edition.
It automatically runs after every commit.
I would love to explore how I could improve this to help Chrome / Mac users too, in case someone finds this interesting.