This is a WIP since months. Shall we close it and move on?

GitHub now has the option for PR authors to turn them into Draft PRs, to show that they're not looking for code review just yet. Perhaps that something for this PR? Or, it can function as a comment on the registered Issue, even if closed.

I'm not sure why @skywinder added WIP since @alexjfisher removed WIP from the title.

We've been using this change at Vox Pupuli for the last few months at least. I Initially, I wasn't sure it'd be good enough, but in practice, it's worked really well.

Can we formulate a test for #encapsulate_string(str) which explains the escaping as a unit test?

It's great to hear that it seems to do the right thing, and thanks for taking the time to follow up.

Example to start from: here I blatantly #send to the private method (which has no instance data dependencies):

# frozen_string_literal: true

module GitHubChangelogGenerator
  RSpec.describe Section do
    let(:options) { { } }
    subject(:section) { described_class.new(options) }

    describe '#encapsulate_string' do
      let(:string) { '' }

      context 'with the empty string' do
        it 'returns the string' do
          expect(section.send(:encapsulate_string, string)).to eq string
        end
      end

      context 'with a string with an escape-needing character in it' do
        let(:string) { '<Inside> and outside' }

        it 'returns the string escaped' do
          expect(section.send(:encapsulate_string, string)).to eq '\\<Inside\\> and outside'
        end
      end
    end
  end
end

@alexjfisher I have finished writing a tiny unit test for the new kind of input supported that you created. I have kept your commit, and added my own. I'll make a PR to "carry" these commits into master. Hope that's alright!

Thanks for the contribution!