There's no single standard, but most teams use one of two shapes. Knowing which one your team uses tells you what 'merged' means for them.
TWO COMMON SHAPES
SHAPE A - MAIN PLUS SHORT BRANCHES (most common)
main ------------------------------------------->
\ / \ / \ /
feature fix feature
Every branch is small and lives 1-4 days. main is
always releasable. Simple, and increasingly the default.
SHAPE B - MAIN, DEVELOP, RELEASE BRANCHES
main ------------------M------------M-------->
release ----R------/ ---R--/
develop ---D----D----D----D----D----D----D------>
\ / \ /
feature branches
Work collects on develop, is cut into a release,
tested, then merged to main. Common where releases
are scheduled rather than continuous.
ASK WHICH ONE YOU HAVE. In Shape A, merged to main
usually means nearly live. In Shape B it can mean
another two weeks.
This Is the Single Most Useful Thing to Ask
'When something merges, how long until a customer sees it?' The answer might be twenty minutes or it might be a fortnight, and it entirely changes how you read every PR from then on. Ask once, write it down.