| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
The workspace-only install omits required root dependencies, leaving warning and resolution comment scripts at risk of module-loading failures in CI.
1 open issue What changed in this PRActivates warnings for direct CHANGELOG.md edits in repository PR checks, using the comment action supplied by prerequisite #4217. Production CodeQL workflows are unaffected.
Changes:
| File | Description |
|---|---|
| .github/workflows/pr-checks.yml | Wires changelog detection and warning/resolution comments into PR checks while preserving repo-size commenting. |
Review effort: Balanced (auto)
Sorry, something went wrong.
Split workflow activation from #4217 while keeping the comment action loaded from trusted main. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
This PR adds a PR check for non-release/mergeback/update-bundle PRs. The check posts a sticky PR comment if CHANGELOG.md has been modified in the PR, warning the author to instead direct their change to a change-note.
This PR is split-off from #4217, which retains the prerequisite post-comment Action.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types: None of the production workflow types; only this repository's PR checks.
Products: No production analysis behavior changes.
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist