I think you’ve misunderstood the situation. I’ve mentioned this 3 or 4 times now in the thread, but to clarify again…
There are two Netlify sites:
Site A - chorus-app.netlify.app. This is the site in Michael Pumo’s Netlify account which is working as expected
Site B - choruslondon.netlify.app. This is the site in Chorus London’s Netlify account which is not working as expected
There are two GitHub repo links we’ve been discussing:
GitHub A - github/michaelpumo/Chorus. This is the repo from which Site A is built.
GitHub B - github/ChorusAgency/Chorus. This is the repo from which Site B is built.
The point I’ve made numerous times in this thread, which doesn’t appear to be acknowledged/believed by you or your colleagues, is that GitHub A is the same repo as GitHub B.
But why are there two different links?
Michael developed the site for us initially. As a result, it was built and pushed to his own GitHub account, github/michaelpumo. Michael also set up the hosting of the site on Netlify while the repo was still under his own GitHub account. This is why when you go into Michael’s dashboard and look at Site A, you see the current repository as this link - github/michaelpumo/Chorus.
After Michael finished with the project, he transferred the GitHub repo from his own account, to our account, github/ChorusAgency. When he did that, the repo moved from github/michaelpumo/Chorus to github/ChorusAgency/Chorus.
Want proof? You guys can’t see this since the repo is private, but I recorded a screencast proving that visiting the url for GitHub A results in a redirect to GitHub B. See the Loom video linked in this post - One codebase, two different deployment results? - #7 by ChorusAgency.
The reason this redirect is happening is because it’s the same repo, just with a new url because it was moved. Even though the url is different, the repo is the same.
You mentioned that one of the sites has 98 vs 99 files. There’s a reason for this…
We have a webhook from our headless CMS (Prismic) set up on Site B. We do not have a webhook for our headless CMS set up on Site A. What this means is, if there is a change to the content in Prismic, Site B is automatically rebuilt with the changed Prismic content incorporated. Site A is not automatically rebuilt.
Could this be the cause of the issue then? No. The issue was still there last time we pushed a change to the GitHub repo, which in turn caused Netlify to rebuild both Site A and Site B. This put the content in a state of exact alignment, but the problem was still there.
As I’m sure you can understand, there’s been 23 days since this topic was first opened, so of course there have been changes in the Prismic repo. I can push a change to the GitHub repo to align the content of Site A and Site B again if you want, just to prove the point to you that this is not the source of the issue?
So given the above points, the assertion that you’re making (which is that they’re different codebases, and this explains the difference in behaviour) is entirely wrong.
Given all of the above, I still don’t see this issue as resolved as you continue to insinuate that the difference between Site A and Site B is caused by differences in the codebase, which it’s patently not. I thought @luke may have been along the right lines when he pointed out that there were differences in the Netlify settings between Site A and Site B (specifically the build image), but aligning the build images didn’t fix the issue.
Again, I cannot understand how two sites being built from an identical codebase can be having different outcomes here, and no one else seems to be able to offer a proper explanation for it.
This issue is now over 3 weeks old, is there any way to escalate it? I don’t think dealing with multiple people is helping as whenever someone new responds they don’t seem to have read and fully understood the context of the issue.