semantic-release / semantic-release/github

Skip Creating Comment if no permission

Open
#1,035 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
534
Forks
150
Avg merge
1m
Merged PRs (30d)
3

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the @semantic-release/github comment-creation path and reproduce the permission-denied case shown in the issue and linked CI logs. Verify that a release completes without attempting or failing on the comment when GitHub denies permission.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, javascript
Domain
api, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.