I work on a new CICD, replacing Jenkins-X 2 by GitHub Actions.

After seeing a lot of actions to create a release + changelog, I found that a lot of them are trigger by a tag on a commit to launch the workflow.

For now, I create a new release on every push on master (merged pr), with a version tag (v1.0.0), via conventional commit.

What is the benefit for me or Lead team to manually create a tag to generate a new release + changelog ?

What is the logic behind that ?

NOTE: I would like to know what is the benefit of "Creating a tag manually to run a release pipeline (including the changelog)" instead of automate the whole process (e.g: if a PR is merged on master, so it automaticaly create the release)

I work on a new CICD, replacing Jenkins-X 2 by GitHub Actions.

After seeing a lot of actions to create a release + changelog, I found that a lot of them are trigger by a tag on a commit to launch the workflow.

For now, I create a new release on every push on master (merged pr), with a version tag (v1.0.0), via conventional commit.

What is the benefit for me or Lead team to manually create a tag to generate a new release + changelog ?

What is the logic behind that ?

EDIT: I would like to know what is the benefit of "Creating a tag manually to run a release pipeline (including the changelog)" instead of automate the whole process (e.g: if a PR is merged on master, so it automaticaly create the release)

I work on a new CICD, replacing Jenkins-X 2 by GitHub Actions.

After seeing a lot of actions to create a release + changelog, I found that a lot of them are trigger by a tag on a commit to launch the workflow.

For now, I create a new release on every push on master (merged pr), with a version tag (v1.0.0), via conventional commit.

What is the benefit for me or Lead team to manually create a tag to generate a new release + changelog ?

What is the logic behind that ?

I work on a new CICD, replacing Jenkins-X 2 by GitHub Actions.

After seeing a lot of actions to create a release + changelog, I found that a lot of them are trigger by a tag on a commit to launch the workflow.

For now, I create a new release on every push on master (merged pr), with a version tag (v1.0.0), via conventional commit.

What is the benefit for me or Lead team to manually create a tag to generate a new release + changelog ?

What is the logic behind that ?

NOTE: I would like to know what is the benefit of "Creating a tag manually to run a release pipeline (including the changelog)" instead of automate the whole process (e.g: if a PR is merged on master, so it automaticaly create the release)