You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm having an issue where in a PR where I forgot (or failed) versioning in the title, the run itself hits an error but marks it as successful, meaning the PR can be merged without a valid changelog.
I'm fairly new to Github Actions so I might be missing something obvious, checked the other issues in this repo and saw nothing, so coming here for help.
Moreover, I don't understand the following. It is said that:
For pull_request event:
Generates changelog using Pull Request Titles or Commit Messages made after the last release.
The created CHANGELOG.rst contains wrong description. Commits, listed under Version: v1.1.0, were made before tag v1.0.1 and commit ci, mentioned under Release: v1.0.1, was made before tag v1.0.0. The commits, made for tag v1.1.0 , are not listed. You can check it in Full Changelog links of release notes. All tags were made right after the correspondent PRs were merged in the main branch.
This run failed to find any new commits after the last release, but there were at least 3. Otherwise the PR would not be created ever.
Am I doing something wrong, or my expectations are incorrect?
Describe the bug
Hi, I'm having an issue where in a PR where I forgot (or failed) versioning in the title, the run itself hits an error but marks it as successful, meaning the PR can be merged without a valid changelog.
I'm fairly new to Github Actions so I might be missing something obvious, checked the other issues in this repo and saw nothing, so coming here for help.
Your Environment
Workflow Run URL (if Public Repository):
https://github.com/MoonieGZ/TwoMoons/actions/runs/5298499154/jobs/9590890439
Contents of Your Changelog-CI Workflow File (.yaml File):
Contents of Changelog-CI Configuration File (If Applicable):
Expected behavior
Check to fail when an error occurs.
Actual behavior
Run hits an error but marks check as success.
The text was updated successfully, but these errors were encountered: