Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions .github/workflows/ci-scriv-entries.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# This workflow verifies that the changelod.d entries have been added
# for the changes in the pull request, using the GH CLI to check the changed files in the PR.

name: CI Scriv entries.

on:
pull_request:

jobs:
ci-scriv-entries:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v6
with:
ref: ${{ github.head_ref }}

- uses: actions/setup-python@v6
with:
python-version: 3.13

- name: Check Scriv entries have been added.
env:
GITHUB_TOKEN: ${{ github.token }}
run: |
gh pr view --json files --jq '.files[].path' \
| grep -q "^changelog\.d/.*\.md$" || (echo "No changelog.d entries added or changed." && exit 1)
3 changes: 3 additions & 0 deletions .github/workflows/create-github-release.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,6 @@
# This workflow creates a GitHub release based on the current version
# changed in the PR created by the create-release-pr workflow.

name: Create GitHub release.

on:
Expand Down
4 changes: 4 additions & 0 deletions .github/workflows/create-release-pr.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
# This workflow creates a pull request to bump the version and update the changelog
# according to the semantic versioning type provided as input.
# Once the PR is merged a new GH release should be created using the create-github-release workflow.

name: Create a release pull request.

on:
Expand Down
55 changes: 55 additions & 0 deletions changelog.d/20260116_201552_daniel.quiroga_check_scriv_entries.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
<!--
Create a new changelog entry for every change in the repository.

Please adhere to the following instructions:
* Add a new bullet item for the category that best describes the change.
* You may optionally append "(by @<author>)" at the end of the bullet item,
where @<author> is the GitHub username of the author of the change. These
affiliations will be displayed in the release notes for every release.
* The accepted categories are: Removed, Added, Changed, Deprecated, Fixed,
and Security.
* Indicate breaking changes with a "**BREAKING CHANGE:**" prefix in the
bullet item.

Uncomment the section that is right (remove the HTML comment wrapper).
For top level release notes, leave all the headers commented out.
-->

<!--
### Removed

- A bullet item for the Removed category.

-->

### Added

- A new workflow has been added to verify Scriv is used when opening PRs.

<!--
### Changed

- A bullet item for the Changed category.

-->

<!--
### Deprecated

- A bullet item for the Deprecated category.

-->

<!--
### Fixed

- A bullet item for the Fixed category.

-->

<!--
### Security

- A bullet item for the Security category.

-->