-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use GitHub actions for builds #1207
Merged
+226
−183
Conversation
This file contains 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
0e0ed1b
to
fab404a
Compare
Loading status checks…
…GitHub Pages for the website. Almost everything is on GitHub now, including snapshots, pull request builds, the website and all the automation thereof. Snapshots are uploaded as GitHub release artifacts so they can be downloaded directly. Pull request builds are uploaded as normal GitHub artifacts. The website is built and deployed to GitHub pages as part of the build automation, including the snapshots page and the update check data. See the comments in the GitHub workflow code for more details. As well as standardising on a single platform, this removes the dependency on my personal server and AppVeyor account, which makes things more sustainable and easier for others to collaborate on.
Need to update the readme and the get address for automatic updates. |
I think those addresses will be kept the same because people are already familiar with them. DNS redirection hasn't happened yet. |
Yup, addresses will all remain the same. It might be a couple of days before we get all the DNS changes sorted though. |
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.
Almost everything is on GitHub now, including snapshots, pull request builds, the website and all the automation thereof. Snapshots are uploaded as GitHub release artifacts so they can be downloaded directly. Pull request builds are uploaded as normal GitHub artifacts. The website is built and deployed to GitHub pages as part of the build automation, including the snapshots page and the update check data. See the comments in the GitHub workflow code for more details. As well as standardising on a single platform, this removes the dependency on my personal server and AppVeyor account, which makes things more sustainable and easier for others to collaborate on.
Fixes #658.