skip-ci = false doesn't trigger pipeline with on push tags v*

[kachi-app]

Configuration:

      - name: Generate changelog
        id: changelog
        uses: TriPSs/conventional-changelog-action@v6.0.0
        with:
          preset: "conventionalcommits"
          create-summary: true
          github-token: ${{ secrets.GITHUB_TOKEN }}
          skip-on-empty: "false"
          skip-ci: 'false'

Here is the pipeline result

Release Commits

Tags

Here is my other pipeline:

name: "[Release] Publish Packages"
on:
  push:
    tags:
      - 'v*'
  pull_request:
    types:
      - opened
      - synchronize
    branches:
      - main

However, after TriPSs/conventional-changelog-action push tags, I expect the pipeline should run

Another issues is type: chore, ci, docs is not generated in the changelog. I am aware the preset issue. However based on https://www.conventionalcommits.org/en/v1.0.0/
types other than fix: and feat: are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others. Isn't it should works ?

Thank you

[TriPSs]

I think this is something that GitHub itself does not do (anymore) from commits that are generated inside the CI, to prevent CI loops.

[kachi-app]

Hi @TriPSs , Thank you
I made it work with custom PAT

      - name: Generate changelog
        id: changelog
        uses: TriPSs/conventional-changelog-action@v6.0.0
        with:
          preset: "conventionalcommits"
          create-summary: true
          github-token: ${{ secrets.CHI_GITHUB_TOKEN }}
          skip-on-empty: "false"
          skip-ci: 'false'

Could you please help about the conventionalCommits ? it seems to me that only fix, and feat is working

[TriPSs]

I never used that preset so I would suggest to check it with the authors

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.