I wasn’t able to locate a dedicated “clone” excerpt in the snippet I found, but here’s the Flux documentation on forking—use this as guidance on when you’d choose fork versus clone.
Forking When you fork a project, all its history of changes is preserved. Meaning the forked part can eventually be merged back with the original.
For the complementary “Cloning” section—when you need just a one‐time copy without history—you’ll find it immediately below “Forking” in that same article. If you don’t see it, try refreshing the page or using the search term “cloning” within the Flux docs.
I couldn’t find any Flux documentation specifically on “cloning a component into a new library entry.” It looks like cloning in Flux today applies at the project level only. You may want to raise this in the Flux User Community or check the full docs for any updates:
Wirelessly connects nets on schematic. Used to organize schematics and separate functional blocks. To wirelessly connect net portals, give them same designator. #portal
General Purpose Thick Film Standard Power
and High-Power Chip Resistor
47 kOhms ±5% 0.125W, 1/8W Chip Resistor 0805 (2012 Metric) Automotive AEC-Q200 Thick Film
Features:
- RMCF – standard power ratings
- RMCP – high power ratings
- Nickel barrier terminations standard
- Power derating from 100% at 70ºC to zero at +155ºC
- RoHS compliant, REACH compliant, and halogen free
- AEC-Q200 compliant