Matt Rogers
Matt Rogers
Could you open a PR for this? I'm not entirely sure that I'll add the feature yet but I would like to see your implementation.
It's already been reported and rejected upstream, as noted in the OP. We'll need to fix this ourselves.
> I am not yet entirely clear on the motivation behind this. Is it that we don't ship Jekyll releases as frequently like in the ol' days or is it...
Going to dump updates here as I work on this: Enforcing conventional commits at the PR level looks like so when the check fails: It goes green if the format...
https://github.com/jekyll/jekyll-test-gem-plugin/pull/8 has an example of the release-please workflow running. We *can* keep the existing `History.markdown` file, though it's format changes slightly.
> Move .github/release-please-*.json config and manifest to .github/release-please/*.json ? I'm curious about this one. Why is that important to you? > Automated PR title to remain Release :gem: v${version}. (Skip...
For the rest of the 3.x series, I propose we take both `baseurl` and `base_path` with the added validation for both, deprecate `baseurl` in favor of `base_path` and if we...
I'm not sure that we **can** take it over. I'll look into it.
A PR to address this would be appreciated if you can make time to create one.