Cloning vs Forking Components

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.
Flux Documentation:
Understood. I need just a snapshot. @help how do I clone a component from my project into a new library entry?
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:
Locate export command
Manual copy steps
Copy symbol to library
Create custom part
A
K


No results...

Tantalum Cap 2917-Template No Prop

Tantalum Cap 2917-Template No Prop thumbnail
Tantalum Capacitor 2917 (7343 Metric) Template NO default properties #simplifiedFootprint #noProp

Properties

F

V

Polarized Capacitor

C

Pricing & Availability

Distributor

Qty 1

Controls