Forking vs. Cloning in Flux

quantumjumper

fork this part

110 days

flux

1:10

Evaluating the fork request.

Clarifying the fork task.

Following tool priorities.

Navigating linking rules.

Checking knowledge base.

Preparing changes.

Looking up docs on How do I fork or clone a library part or project in Flux so I can edit it as my own? Steps to duplicate a part from the library (or a published part) into my workspace, including where to click in the UI..

Linking and querying knowledge.

I can’t fork it for you directly. Here’s what the Flux documentation says about forking vs. cloning:

"Whenever you find a publicly accessible project or part in the library, and you decide to duplicate the project, then you will need to decide whether to clone or fork the project.

If you want to maintain access to all earlier versions of the project in your duplicate version, then you should fork the project. This is a common option you would use when experimenting with an earlier version of a design. However, if you do not need to have access to the earlier versions of the duplicate project, then you should clone the project.

Read this resource to learn more about using cloning and forking in Flux.

Merging

Version control systems like Git provide a function called merging, where a forked project is consolidated back into its original branch. At the moment, this capability is not included in Flux. In the future, we will release merging back to the original project." Source

If you want, I can guide you through the exact steps to fork the TIP41CG part in your workspace.

Fork for version history

Clone instead of fork

Edit properties only

Need a custom footprint

Export then reimport

110 days