A ROM thread runs 400 pages and the first post is two years old. Somewhere in there is the one line that decides whether your phone ends the day working or in a boot loop. You can find it in about ten minutes if you read the thread like a manual instead of a hype reel.
Start with the codename, not the marketing name
Builds are made for hardware codenames, and the codename is the only thing that has to match. The Poco F3 is “alioth”, the OnePlus 6 is “enchilada”, the Pixel 3 is “blueline”. The phone in your hand says one thing on the box and another thing in fastboot. Check yours with a device info app before you download anything, because every forum has a thread full of people who guessed.
The first post is a spec sheet
Read it top to bottom once. Three items decide everything: the firmware or baseband requirement, the recovery situation, and the maintainers’ list of broken things. Plenty of builds won’t boot without a newer vendor firmware underneath, and “flash the firmware package first” is buried in bold halfway down. As for recovery, some builds want LineageOS recovery, some want TWRP, and flashing with the wrong one is the most common way a Saturday disappears.
The broken-things list ages fast. Scroll to the last two or three pages and read what’s broken now: VoLTE, the second SIM, the fingerprint reader, camera aux lenses. A maintainer who writes “nothing works on 5G yet” saved you an evening.
Check who is building it and whether they’re still around
LineageOS grew out of CyanogenMod, which started in 2009 and wound down in December 2016, and the fork’s official builds come with named maintainers and a release schedule on the LineageOS wiki. Unofficial builds are a different animal. One person compiles a weekly in their spare time, and the build date tells you whether that’s still true. A three-month-old “latest” zip is a project someone quietly walked away from.
The threads worth reading twice
The bug reports where the OP replies with a log, and the post where someone asks a dumb question and gets a five-line answer with commands. That’s where the actual documentation lives. Screenshots of the setup screen are decoration.
One more habit: after you flash and everything works, wait a week before you tell the thread it’s stable. Daily-driver confidence and first-boot success are different measurements. Ask anyone who lost Bluetooth on day four.