Skip to content

fix(ci): specifying fetch depth in CHANGELOG.md generation #9564

Merged
gcf-merge-on-green[bot] merged 1 commit intomainfrom
fetch_depth
Jun 20, 2023
Merged

fix(ci): specifying fetch depth in CHANGELOG.md generation #9564
gcf-merge-on-green[bot] merged 1 commit intomainfrom
fetch_depth

Conversation

@suztomo
Copy link
Member

@suztomo suztomo commented Jun 20, 2023 •
edited
Loading 

    # Number of commits to fetch. 0 indicates all history for all branches and tags.
    # Default: 1
    fetch-depth: ''

https://github.com/actions/checkout

@conventional-commit-lint-gcf
Copy link

conventional-commit-lint-gcf bot commented Jun 20, 2023

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

@suztomo suztomo added the automerge Merge the pull request once unit tests and other checks pass. label Jun 20, 2023
@gcf-merge-on-green gcf-merge-on-green bot merged commit 0158232 into main Jun 20, 2023
@gcf-merge-on-green gcf-merge-on-green bot deleted the fetch_depth branch June 20, 2023 21:52
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jun 20, 2023
This was referenced Jun 20, 2023
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@burkedavison burkedavison burkedavison approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@suztomo @burkedavison