https://www.freecadweb.org/wiki/index.p ... ent#Access
Here is the diff: https://www.freecadweb.org/wiki/index.p ... did=182842
Changed the orientation from SF to GitHub
Tried to add some git commands to make it more friendly to amateur devs (but the wiki markup wasn't flexible to make it cosmetically sufficient)
Fixed some grammar issues
Added hyperlinks
The rest of the page needs to be reworked so that SF is shown as deprecated. Please advise.
Updated Developer Hub's Source Code Managment
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Updated Developer Hub's Source Code Managment
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Updated Developer Hub's Source Code Managment
May I suggest that you add the git command needed for the actions ?
Create a new branch ---> example command
Checkout that new branch ---> example command
Commit your changes to that new branch ---> example command
Push that new branch to your GitHub repo ---> example command
I think that one must also add an origin to its git repository in order to track the changes on master ---> example command
After that, the user will need to do merges between master and its branch ---> example command
Create a new branch ---> example command
Checkout that new branch ---> example command
Commit your changes to that new branch ---> example command
Push that new branch to your GitHub repo ---> example command
I think that one must also add an origin to its git repository in order to track the changes on master ---> example command
After that, the user will need to do merges between master and its branch ---> example command
Re: Updated Developer Hub's Source Code Managment
Sounds good to me. Please feel free to add them. I don't know CLI git very well, since i've been using a git GUIjean.thil wrote:May I suggest that you add the git command needed for the actions ?
Create a new branch ---> example command
Checkout that new branch ---> example command
Commit your changes to that new branch ---> example command
Push that new branch to your GitHub repo ---> example command
I think that one must also add an origin to its git repository in order to track the changes on master ---> example command
After that, the user will need to do merges between master and its branch ---> example command
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
- kkremitzki
- Veteran
- Posts: 2511
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: Updated Developer Hub's Source Code Managment
Good pick for a page to revise, that was quite out of date. I cleaned it up some more, and I can add more in-depth git commands in a bit.
Re: Updated Developer Hub's Source Code Managment
Thanks! and nice work @kkremitzkikkremitzki wrote:Good pick for a page to revise, that was quite out of date. I cleaned it up some more, and I can add more in-depth git commands in a bit.
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
- kkremitzki
- Veteran
- Posts: 2511
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: Updated Developer Hub's Source Code Managment
This section can probably be deleted but I'd like confirmation from someone who actually knows it's no longer relevant.
Re: Updated Developer Hub's Source Code Managment
Sorry, but if I suggested to add them it is because I don't know very well how to do that.Sounds good to me. Please feel free to add them. I don't know CLI git very well, since i've been using a git GUI
I think that for the firsts commands it should be :
Create a new branch ---> git branch my_branch
Checkout that new branch ---> git checkout my_branch
Commit your changes to that new branch ---> git add modified_file1 modified_file2
git commit -m 'what I have done'
Push that new branch to your GitHub repo---> git push
but I haven't done add an origin to its git repository in order to track the changes on master nor any merge.
Re: Updated Developer Hub's Source Code Managment
Yes. I think it can be deleted. That was the policy we had on SVN, but with git it's not necessary to give write permission to everybody anymore...kkremitzki wrote:This section can probably be deleted but I'd like confirmation from someone who actually knows it's no longer relevant.