Thank you! When I stumble across the Neovim posts, I try to share them here if I think someone will find them useful.

I stumbled upon this article as I was having issues with my LSP setup for TypeScript projects. However, in my case, it appears the bug is in the plug-in nvim-lspconfig.

I know what you mean. Quite often when I’ve worked in a project where there is a pull request template, a lot of the time people don’t bother to fill it out. However, in an ideal world, people would be proud of the work that they’ve delivered, and take the time to describe the changes when raising a pull request.

Oh, it’s not my own blog, I just stumbled upon it, and wanted to share the post.

After a bit of experimentation, I’ve managed to find a cleaner solution to enforcing the ticket number in the subject:

module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    // Enforce scope to match JIRA ticket format like PER-123
    'jira-ticket-rule': [2, 'always'],
    'subject-case': [0],
  },
  plugins: [
    {
      rules: {
        'jira-ticket-rule': ({ subject }) => {
          return [
             subject && subject.match(/[A-Z]+-\d+/),
            'Your subject should contain a JIRA ticket eg PER-123',
          ];
        },
      },
    },
  ],
};