Build in Appveyor #375
Merged
Build in Appveyor #375
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
|
I've enabled it for my fork, and it works well: |
|
Awesome! I’ll put it on my todo list for this week. |
ashawley
force-pushed
the
appveyor
branch
2 times, most recently
from
b45f4a0
to
1b8a842
Compare
|
@johno Could you try enabling Appveyor for Pixyll, at some point? Start here: https://ci.appveyor.com/login If it works, then merge this branch. |
|
Done, thanks @ashawley |
|
Cool, thanks! Did you see a build happen? I was expecting Appveyor would be running for pull requests or merges to master. I'm looking here, https://ci.appveyor.com/project/johno/pixyll, but not seeing anything. |
|
Oh whoops, looks like I didn't fully add it. Should be g2g now https://ci.appveyor.com/project/johno/pixyll |
|
🚀 Looking good! Awesome, thanks. |
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.
Automated builds specifically on Windows may benefit those users. Although, I predict it isn't necessary: The entire stack (Ruby, bundler, Jekyll) should be so portable these days that it is of no concern.
However, maybe there's a chance this is generally useful as a starting point to some users. Appveyor would be the recommendation. And a Windows build may be helpful should we run in to issues specific to Windows users with gem-based themes for #333 and #360.
Before merging this, @johno would need to sign-in at Appveyor and enable this repo.