Grouping some keybindings that don't share the same first letter

[xfzv]

With legendary.nvim, I can group the following keybindings:

{
        itemgroup = "Buffers",
        description = "Buffers commands",
        icon = " ",
        keymaps = {
          {
            "<S-TAB>",
            function()
              require("bufferline").cycle(-1)
            end,
            description = "Previous buffer",
          },
          {
            "<TAB>",
            function()
              require("bufferline").cycle(1)
            end,
            description = "Next buffer",
          },
          {
            "<leader>bh",
            function()
              require("bufferline").move(-1)
            end,
            description = "Move buffer backward",
          },
          {
            "<leader>bl",
            function()
              require("bufferline").move(1)
            end,
            description = "Move buffer forward",
          },
        },
},

With which-key.nvim, the <S-TAB> and <TAB> keybindings will be displayed separately (not in the Buffers group), because they don't start with b key.

I know the whole concept of which-key.nvim is to display the available keybindings in a popup as you type, just wondering if there's a way to achieve this regardless.

Assuming this is not possible, I'm curious to know how other users organize keybindings that are related but have different letters.

For example, I also have:

{
        itemgroup = "Git",
        description = "Git commands",
        icon = "",
        keymaps = {
            "<leader>gn",
            function()
              require("gitsigns").next_hunk()
            end,
            description = "Next hunk",
          },
          {
            "<leader>gN",
            function()
              require("gitsigns").prev_hunk()
            end,
            description = "Previous hunk",
          },
          {
            "<leader>gp",
            function()
              require("gitsigns").preview_hunk()
            end,
            description = "Preview hunk",
          },
          {
            "<leader>gr",
            function()
              require("gitsigns").reset_hunk()
            end,
            description = "Reset hunk",
          },
          {
            "<leader>lg",
            function()
              require("lazygit").lazygit()
            end,
            description = "LazyGit",
          },
},

Using <leader>lg for lazygit.nvim makes sense to me, and so does grouping it with gitsigns.nvim commands in a Git group.