Skip to content
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

Add support for Jekyll 4.0 #1

Merged
merged 1 commit into from Jan 17, 2020
Merged

Add support for Jekyll 4.0 #1

merged 1 commit into from Jan 17, 2020

Conversation

David-Byrne
Copy link
Owner

jekyll/jekyll#7591 was failing builds that use Jekyll 4.0, as Github Actions use a lot of the same infrastructure as Azure Pipelines (so much so that they even share bugs!)

jekyll/jekyll#7591 was failing builds
that use Jekyll 4.0, as Github Actions use a lot of the same
infrastructure as Azure Pipelines (so much so that they even
share bugs!)
@David-Byrne David-Byrne merged commit 8eb54bf into master Jan 17, 2020
@David-Byrne David-Byrne deleted the jekyll4 branch January 17, 2020 20:58
David-Byrne added a commit that referenced this pull request Mar 8, 2020
There's been a few issues with Jekyll-Diff-Action
using the default `/github/workspace` directory
to run in. That's mounted in read only mode, so
any command that tried modify it failed (see PR #1
and issue #2).
To get away from all this, this PR adds an initial
step to the diff script to create our own workspace
with the appropriate permissions.
David-Byrne added a commit that referenced this pull request Mar 8, 2020
There's been a few issues with Jekyll-Diff-Action
using the default `/github/workspace` directory
to run in. That's mounted in read only mode, so
any command that tried modify it failed (see PR #1
and issue #2).
To get away from all this, this PR adds an initial
step to the diff script to create our own workspace
with the appropriate permissions.
David-Byrne added a commit that referenced this pull request Mar 8, 2020
There's been a few issues with Jekyll-Diff-Action
using the default `/github/workspace` directory
to run in. That's mounted in read only mode, so
any command that tried modify it failed (see PR #1
and issue #2).
To get away from all this, this PR adds an initial
step to the diff script to create our own workspace
with the appropriate permissions.
David-Byrne added a commit that referenced this pull request Mar 8, 2020
There's been a few issues with Jekyll-Diff-Action
using the default `/github/workspace` directory
to run in. That's mounted in read only mode, so
any command that tried modify it failed (see PR #1
and issue #2).
To get away from all this, this PR adds an initial
step to the diff script to create our own workspace
with the appropriate permissions.
David-Byrne added a commit that referenced this pull request Mar 9, 2020
There's been a few issues with Jekyll-Diff-Action
using the default `/github/workspace` directory
to run in. That's mounted in read only mode, so
any command that tried modify it failed (see PR #1
and issue #2).
To get away from all this, this PR adds an initial
step to the diff script to create our own workspace
with the appropriate permissions.
David-Byrne added a commit that referenced this pull request Mar 9, 2020
There's been a few issues with Jekyll-Diff-Action
using the default `/github/workspace` directory
to run in. That's mounted in read only mode, so
any command that tried modify it failed (see PR #1
and issue #2).
To get away from all this, this PR adds an initial
step to the diff script to create our own workspace
with the appropriate permissions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant