AGENTS.md:154 says "Our CI validates semantic PR titles (see .github/workflows/pr_lint)".
The file is valid, complete YAML — name: lint | PR, amannn/action-semantic-pull-request@v5 with the full type list, and a release-drafter/release-drafter@v6 step. But it has no .yml or .yaml extension, and GitHub Actions only picks up workflows that do.
The API confirms it server-side: the repository has 74 registered workflows and none whose path contains pr_lint, while a control (basic_tests.yml) shows up as active.
ls -1 .github/workflows/ | grep -vE '\.(yml|yaml)$'
# disable_independent_workflows.sh
# pr_lint
gh api "repos/topoteretes/cognee/actions/workflows?per_page=100" --jq '.total_count'
# 74
gh api "repos/topoteretes/cognee/actions/workflows?per_page=100" \
--jq '[.workflows[] | select(.path | test("pr_lint"))] | length'
# 0
The path was created without an extension in fbc9cefda (2025-01-10), so it looks like it never ran rather than having regressed. require-linear-issue.yml checks for a Linear key, which is a different rule, so semantic PR titles appear to be unenforced today. The release-drafter step in the same file would be inactive for the same reason.
Observed at 8b86f868fcab8d688b41f430e4cc7be1d8427e11.
Possible fix: rename to pr_lint.yml. Worth a look at whether the current PR titles would pass the configured type list before turning it on.
AGENTS.md:154says "Our CI validates semantic PR titles (see.github/workflows/pr_lint)".The file is valid, complete YAML —
name: lint | PR,amannn/action-semantic-pull-request@v5with the full type list, and arelease-drafter/release-drafter@v6step. But it has no.ymlor.yamlextension, and GitHub Actions only picks up workflows that do.The API confirms it server-side: the repository has 74 registered workflows and none whose path contains
pr_lint, while a control (basic_tests.yml) shows up asactive.The path was created without an extension in
fbc9cefda(2025-01-10), so it looks like it never ran rather than having regressed.require-linear-issue.ymlchecks for a Linear key, which is a different rule, so semantic PR titles appear to be unenforced today. Therelease-drafterstep in the same file would be inactive for the same reason.Observed at
8b86f868fcab8d688b41f430e4cc7be1d8427e11.Possible fix: rename to
pr_lint.yml. Worth a look at whether the current PR titles would pass the configured type list before turning it on.