Skip to content
Draft
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
4 changes: 4 additions & 0 deletions .github/workflows/tests-python.yml
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# -*- coding: utf-8 -*-
#
# Copyright (C) 2024 CERN.
# Copyright (C) 2025 Graz University of Technology.

name: Python CI

Expand Down Expand Up @@ -44,6 +45,9 @@ jobs:
- name: Checkout
uses: actions/checkout@v4

- name: commitlint
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what the default config is for commitlint, but I see there are many of flexible options and even "shared configurations" (similar to ESLint).

I would prefer that we have a "global" config with the set of allowed types (i.e. chore, feat, fix, etc.). Regarding topics (i.e. whatever goes in fix(<topic>): ...) I see that we:

  • have a set of global topics
  • repo-specific topics where applicable via their own .commitlintrc?

uses: wagoid/commitlint-github-action@v6
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor: for 3rd-party action (i.e. those that are not under the "official" actions/ namespace), I prefer that we reference them by their commit hash with the intedned tag/version in a comment

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be clear, using the commit hash is for security + breaking change shield purposes, right? As in, we use v6 and a rogue action update to 6.1 introduces a vulnerability or breaks the CI? (must admit that for our own repos and at least docs-invenio-rdm I haven't been that paranoid )


- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v5
with:
Expand Down