Repository navigation
Conversation
skshetry
force-pushed
the
debug/heroku-git-history
branch
from
October 26, 2026 04:21
3bc61f2 to
21fabba
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Temporary diagnostic, not meant to be merged.
Sitemap
lastmoddates would need git history at build time. Heroku builds from the GitHub integration likely get a source tarball without.git, but nothing in the current build log confirms it. This prints, beforeyarn buildinscripts/heroku-deploy.sh:SOURCE_VERSION.gitexists, and if so whether the clone is shallow and the last commit date ofcontent/docs/start/index.mdCheck the review app build log, then close this PR.
🤖 Generated with Claude Code