Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from Jun 20, 2023

Conversation

suztomo
Copy link
Member

@suztomo suztomo commented Jun 20, 2023

    # 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

🤖 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
28 of 30 checks passed
@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants