digitalMoksha

Don't know if it would be helpful or not, but here's the GitLab CI configuration we use for the [GLFM](https://gitlab.com/gitlab-org/ruby/gems/gitlab-glfm-markdown/-/blob/main/.gitlab-ci.yml?ref_type=heads) gem, with the release trigger being in a shared component...

So with ya'lls permission, wanted to try to release a 0.24.0 (or 0.23.1) with the new wiki link support. I just want to clarify the first step, _Bump version in...

Just tried - at the moment it doesn't work, which makes sense - the PR title, changelog comparison, and the branch name are built using the new version number. See...

Of course `main` is protected. Creating PR https://github.com/kivikakk/comrak/pull/415

https://github.com/kivikakk/comrak/pull/416 was created by release workflow. But I don't have permission to merge it without all checks passing. I removed the `[skip test]` in the PR title. But I don't...

Yep, that's what happens when trying to do something when enough coffee hasn't been consumed - you gloss over clearly written text. 🤦

Sorry to keep poking in different directions :-) I would still come down on the side of sticking with adherence to CommonMark conventions, whether that's how links are handled, or...

@G-Rath @mattbrictson I've just pulled in `3.19.0`. When I deploy (to staging in this case), the deploy hangs in `set_current_revision_time`. It never returns. This is a git deploy. Here is...

I've opened https://github.com/capistrano/capistrano/issues/2161

This works, but I hooked it before the normal bracket link processing cause it turned out to be much easier/cleaner, but I now realize it bypasses the normal inline processing...