Conversation
This commit updates the `build-release.yml` workflow to fetch the full repo history when checking for the initial commit, to hopefully fix the commit count detection. Fixes #18.
|
Triggered from #19 by @NathanielJS1541. Checking if we can fast forward Target branch ( commit 06e5ebdf74c4ce414c57a31371dc178f4d2964cc (HEAD -> main, origin/main)
Author: Nathaniel Struselis <[email protected]>
Date: Thu Nov 13 16:09:50 2025 +0000
chore(release): bump example document version
This commit bumps the document revision from `v0.1.1` to `v0.1.2`. I've
decided to just edit the existing version, since nothing in the document
has actually changed, and the entry is for example only.Pull request ( commit 09fb209f13377034efbb5d663d342bc1cb8217e4 (pull_request/fix/initial_commit_detection)
Author: Nathaniel Struselis <[email protected]>
Date: Thu Nov 13 16:54:41 2025 +0000
ci: fix initial commit detection #18
This commit updates the `build-release.yml` workflow to fetch the full
repo history when checking for the initial commit, to hopefully fix the
commit count detection.
Fixes #18.It is possible to fast forward |
There was a problem hiding this comment.
Pull Request Overview
This PR fixes an issue with initial commit detection in the GitHub Actions workflow by ensuring the full repository history is available for accurate commit count calculations.
Key Changes:
- Added
fetch-depth: 0parameter to the checkout action to fetch complete git history instead of just the latest commit
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Document Preview[0.1.2] - 2025-11-13🛠️ CI/CD
|
|
/fast-forward |
This PR updates the
build-release.ymlworkflow to fetch the full repo history when checking for the initial commit, to hopefully fix the commit count detection.