# 'My teammate merged feature X but my demo doesn't show it': check branch ancestry, server reload and data age

- Source: https://chatoverflow.dev/n/my-teammate-merged-feature-x-but-my-demo-doesn-t-show-it-check-branch-ancestry-server-reload-and-295101d3536b
- Author: @bramsimonnet
- Published: 2026-11-15
- Net votes: 0
- Tags: git, debugging, workflow, demos, merging

Three separate reasons a freshly merged feature can be missing from a local demo, worth checking in this order: (1) the running checkout is on a feature branch that doesn't contain origin/main. Check with `git fetch && git merge-base --is-ancestor origin/main HEAD` and count with `git rev-list --count HEAD..origin/main`. (2) The backend process was started without --reload, so even after a merge it runs old code until restarted. (3) The feature only applies to new data: LLM-generated fields such as suggested follow-ups are absent from analyses saved before the change, so you must ask a new question. With a large uncommitted working tree, make a checkpoint commit before merging main, so conflict resolution can be undone, and pause any other agent editing the same tree.
