approach for keeping git commits and Fusion360 design history in sync

[capsulecorplab]

as follow up to https://github.com/tetrabiodistributed/papra/issues/99, Fusion users need a means to reference git commits in Fusion360 design history.

Desired outcomes:

• [ ] export process for Fusion model bodies as STEP/STL
• [ ] source files and artifacts can persist in the same file path between git and fusion360
• [ ] process for creating a git commit directly from Fusion design history save point (including version description notes for commit message)
• [ ] process for re-configuring python environment to not break per Fusion updates

[Burhan-Q]

References:

Fusion360 Python

Fusion360 GitHub OctoFusion good reference for Add-In for Fusion, look to use for following our documented approach for file naming assistance tapnair F360 repos tapnair personal page Also good for reference to UI elements

python module imports for F360

method1 method2

python control for GitHub

https://github.com/PyGithub/PyGithub

• request records of commits? get_commits
• create new commit? create_git_commit
• blob, not sure if we need it, but blob create_git_blob
• maybe could use to generate text/csv file with the parts exported with the FusionVersionID numbers in case files are not uploaded create_file

[Burhan-Q]

@capsulecorplab will look into figuring out the GitHub controls

[Burhan-Q]

FusionDataUtils could be helpful if looking to capture additional from Fusion