feat: allow to have a custom configuration per branches

[KillianHmyd]

This could allow to have different behaviours according to the branch from which the release is triggered. For example the following example would allow to have changelog only from lts/* and master branches in two different channels :

[
      "semantic-release-slack-bot",
      {
       "notifyOnSuccess": false,
        "notifyOnFail": false,
        "branchesConfig": [
           {
             "branchPattern": "master",
             "notifyOnSuccess": true,
             "notifyOnFail": true,
             "slackWebhook": "stable-channel",
          },
           {
             "branchPattern": "lts/x",
             "notifyOnSuccess": true,
             "notifyOnFail": true,
             "slackWebhook": "lts-channel",
          }
       ]
      }
    ]

[juliuscc]

I have a question. I saw you used micromatch. Is that the same pattern-strategy that is used by semantic-release (see here)? It should work identically I think, as a subtly different behavior would be a large cause of friction for users.

[KillianHmyd]

Yes it is exactly the same 👍 If you check the link they put on glob it redirects to micromatch documentation.
It is also referenced in their package.json and seems to be used to filter the branches here.

[juliuscc]

I've looked through the PR and it's great! You have great tests and I think the implementation is clear. It's also great that you expanded the example in the readme.

If you fix the small spelling/grammatical nitpicks I will merge 👍

[KillianHmyd]

I've pushed your suggestions, thanks !
Also we tested it in one of our private repository and it worked well 👍

[juliuscc]

Looks great! Thanks! 👍

[juliuscc]

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀