Add a GitHub workflow #4
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
derrickstolee
approved these changes
May 3, 2021
It is really convenient to be able to use GitHub Actions to run automated tasks, such as creating the Git for macOS installer. This adds a GitHub workflow definition to do exactly that. It can be triggered manually from the Actions tab of the `git_osx_installer` repository on GitHub. For details, see https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch Alternatively, the `push:` line can be uncommented so that a simple push triggers the workflow. Signed-off-by: Johannes Schindelin <[email protected]>
With this change, we do not have any hard-coded fallback for the ref anymore, but always build the latest available tagged Git version. Signed-off-by: Johannes Schindelin <[email protected]>
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.
With this PR, it should be a lot easier to build new installers. An example run can be found here.
The workflow can be triggered manually. Alternatively, the
push:line can be uncommented and at the next push, the latest Git will be built.Please note that this PR only builds unsigned installers for now. If this experiment goes well, we should probably look into integrating an optional signing step (conditional on the presence of certain Actions secrets).
This is a companion PR for timcharper#156.