Skip Creating Comment if no permission

[MrGadget1024]

Current behavior

[11:28:49 AM] [semantic-release] » i  Start step "success" of plugin "@semantic-release/github"
2025-04-28T11:28:51.612Z semantic-release:github found pull requests: [ 4019 ]
2025-04-28T11:28:51.614Z semantic-release:github create comment: {
  owner: 'MirrorNetworking',
  repo: 'Mirror',
  issue_number: 4019,
  body: ':tada: This PR is included in version 96.6.2 :tada:\n' +
    '\n' +
    'The release is available on [GitHub release](https://github.com/MirrorNetworking/Mirror/releases/tag/v96.6.2)\n' +
    '\n' +
    'Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:'
}
[11:28:52 AM] [semantic-release] [@semantic-release/github] » ×  Not allowed to add a comment to the issue/PR #4019.

Expected behavior

Skip if no permission

semantic-release version

latest

CI environment

GitHub

Plugins used

  plugins: [
    [ '@semantic-release/commit-analyzer', [Object] ],
    [ '@semantic-release/release-notes-generator', [Object] ],
    [ '@semantic-release/exec', [Object] ],
    [ '@semantic-release/exec', [Object] ],
    [ '@semantic-release/exec', [Object] ],
    [ '@semantic-release/exec', [Object] ],
    [ '@semantic-release/github', [Object] ]
  ],

semantic-release configuration

https://github.com/MirrorNetworking/Mirror/blob/master/.github/workflows/Semantic.yml
https://github.com/MirrorNetworking/Mirror/blob/master/.releaserc.yml

CI logs

https://github.com/MirrorNetworking/Mirror/actions/runs/14706637272/job/41268518316

[babblebey]

This is specific to the "@semantic-release/github" plugin... will transfer

[babblebey]

Hey @MrGadget1024,

Provided you have @semantic-release/github installed as plugin in your release config, its implied that you are ready to give permission required to allow the plugin make every necessary communication with your repo, see required permissions here - https://github.com/semantic-release/github?tab=readme-ov-file#github-authentication - following this you can then choose to not write comment to you release associated PR and Issues if you wish, see config options using the successCommentConditions - https://github.com/semantic-release/github?tab=readme-ov-file#successcommentcondition-example

But, I gotta ask though... Is this causing your release to fail???

The linked release job result is expired