It's how I set up my environment when I work with Github or Gitlab
I fork via the GUI (Pressing the 'Fork' button). Then I clone the fork to my local machine. And then I set the 'upstream' manually to point to the upstream repo.
upstream is the original repo you forkedHarryvL wrote: ↑Mon Oct 08, 2018 2:36 pm
Code: Select all
$ git config --local --list | grep origin | grep github remote.origin.url=https://github.com/FreeCAD/FreeCAD.git firstname.lastname@example.org:PrzemoF/FreeCAD.git
I updated my fork today as per the following advice: https://github.com/KirstieJane/STEMMRol ... he-browser
I get the point . Thanks for the tip. It's going to be one heck of a dive at the deep end for me.bernd wrote: ↑Mon Oct 08, 2018 8:19 pmbranch assess looks good to me. To get it first started I would go for the following.
- in module src/Mod/Fem/femsolver/oofem/writer.py define a string testinputfile = ''' an simple complete oofem input file '''
- in method def write_OOFEM_input(self): ( https://github.com/HarryvL/FreeCAD/blob ... py#L64-L81 ) you gone write the string testinputfile
- means no matter what FreeCAD analysis for objects has, if it has an oofem solver object in any case your testinputfile will be written.
- With this you can test if the new solver object works at all.
- if it works you can start to step by step implement the writer for oofem which does write the real FreeCAD object data to the oofem input file.
Hope you got my point. It is just an idea, how I did it when I mplemented the Z88.