Conversation
| Git is nowadays probably the most common Version Control System for Software Development. Version Control is mainly used to create a development history | ||
| during development. This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams |
There was a problem hiding this comment.
| Git is nowadays probably the most common Version Control System for Software Development. Version Control is mainly used to create a development history | |
| during development. This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams | |
| Git is nowadays probably the most common Version Control System for Software Development. Version Control is used to create a change history during development. | |
| This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams |
| during development. This reduces the potential of data loss and enables one to easily reset changes. Furthermore, in professional software development teams | ||
| Version Control can be used to review the work of colleagues to improve code quality and reduce the potential for bugs. | ||
|
|
||
| Within this lecture we will not actively use Git, but GitHub to provdie you with the relevant code for your laboratory sessions. |
There was a problem hiding this comment.
| Within this lecture we will not actively use Git, but GitHub to provdie you with the relevant code for your laboratory sessions. | |
| Within this lecture we will not actively use Git, but provide you with the corresponding code for your lab sessions via GitHub. |
| Version Control can be used to review the work of colleagues to improve code quality and reduce the potential for bugs. | ||
|
|
||
| Within this lecture we will not actively use Git, but GitHub to provdie you with the relevant code for your laboratory sessions. | ||
| Therefore, mainly one feature of Git is necessary - cloning a repository. Those who want to know more about Git, should take a look at the [References](#references) |
There was a problem hiding this comment.
| Therefore, mainly one feature of Git is necessary - cloning a repository. Those who want to know more about Git, should take a look at the [References](#references) | |
| Therefore, mainly one feature of Git is necessary - cloning a repository, which will be explained within this manual. | |
| Those who want to know more about Git, should take a look at the [References](#references) |
| Therefore, mainly one feature of Git is necessary - cloning a repository. Those who want to know more about Git, should take a look at the [References](#references) | ||
|
|
||
| ## Git Clone | ||
| If not stated otherwise within the repositories README, cloning a git repository is always the same and requires the below 3 steps. |
There was a problem hiding this comment.
| If not stated otherwise within the repositories README, cloning a git repository is always the same and requires the below 3 steps. | |
| If not stated otherwise within the repositories README, cloning a git repository is always the same and requires the below two steps. |
Third step is optional after the first time done, isn't it?
|  | ||
| ### 2. Open MPLAB X IDE and clone the current repository | ||
| --- | ||
| Before you start, make sure that all your old projects are closed. |
There was a problem hiding this comment.
Why that? I MPLAB running into issues if there are open projects?
If so, I guess we have to explain how to close a proejct.
There was a problem hiding this comment.
If the project is open you can not clone a new git repository but it is possible to work in the opend one
| ### 2. Open MPLAB X IDE and clone the current repository | ||
| --- | ||
| Before you start, make sure that all your old projects are closed. | ||
| To clone the repository please follow the instructions: |
There was a problem hiding this comment.
| To clone the repository please follow the instructions: | |
| To clone the repository please follow the below instructions: |
| 4. choose in the toolbar TEAM | ||
| 5. choos GIT --> clone | ||
| 6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next | ||
| 7. select main as your remote Branche, select Next |
There was a problem hiding this comment.
| 7. select main as your remote Branche, select Next | |
| 7. select main as your remote Branch, click Next |
| 3. close all open projects | ||
| 4. choose in the toolbar TEAM | ||
| 5. choos GIT --> clone | ||
| 6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next |
There was a problem hiding this comment.
| 6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next | |
| 6. enter the repository link and choose the Destination Folder U://Microcontroller, click Next |
| 3. close all open projects | ||
| 4. choose in the toolbar TEAM | ||
| 5. choos GIT --> clone | ||
| 6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next |
There was a problem hiding this comment.
| 6. enter the repository link and choose the Destination Folder U://Microcontroller, select Next | |
| 6. enter the repository link and choose the Destination Folder U:/Microcontroller, select Next |
Are two slashes (//) required? I'm not sure right now.
|
|
||
|  | ||
|
|
||
| If you want your repository to be stored in a different folder simply change the location from *U:\Microcontroller\* to you prefered location. But keep in mind that it's harder to support you in case you use a different setup. |
There was a problem hiding this comment.
| If you want your repository to be stored in a different folder simply change the location from *U:\Microcontroller\* to you prefered location. But keep in mind that it's harder to support you in case you use a different setup. | |
| If you want your repositories to be stored in a different folder simply change the location from *U:/Microcontroller/* to your preferred location. But keep in mind that it's harder to support you in case you use a different setup and that **you need to make sure that _C_LIB is always positioned correctly**! |
| --- | ||
| Before you start, make sure that all your old projects are closed. | ||
| To clone the repository please follow the instructions: | ||
|  |
There was a problem hiding this comment.
Sadly the GIFs resolution is not that good, within the README.
Either tell them to click on it to have a better resolution, or focus the GIF on the Git window and add a screenshot to show how to open it via Team -> Git -> ....
There was a problem hiding this comment.
I tried to re film it, can you check the quality ? It lookes quite good on my laptop
There was a problem hiding this comment.
Still can't read the links. But as you added a written manual too, we should give it a try ;) :)
| > [!WARNING] | ||
| > In case you already cloned the library into your working folder - **do not clone it a second time!** | ||
|
|
||
|  |
There was a problem hiding this comment.
Same as for the other GIF, resolution within the README is very low...
Would re-record it, showing only the Git window.
There was a problem hiding this comment.
I will add written discrption and try a different tool
| This repository contains all relevant documentation for tools, libraries etc. used within the lectures. Below links lead you to the related documentation. Just click on them to open it. :) | ||
|
|
||
| 1. [Git](git.md) | ||
|
|
There was a problem hiding this comment.
Please don't use empty lines in enumerations.
It's confusing to read (in source mode) and I don't know if it can lead to rendering issues.
| To clone the repository please follow the instructions: | ||
|  | ||
| Before you start, make sure that all your old projects are closed. To do so, you need to right-click on the microcontroller symbol of your current project shown in the left-hand column and then select *close*. | ||
| To clone the repository please the below instructions: |
There was a problem hiding this comment.
| To clone the repository please the below instructions: | |
| To clone the repository please follow the below instructions: |
| For those who do like to have written instructions: | ||
| 1. Open the [GitHub repository _C_LIB](https://github.com/MicrocontrollerApplications/_C_Lib) | ||
| 2. Copy the repository link (see ### 1.) | ||
| 3. follow step 2. to 8. of the in ### 2. described instructions |
There was a problem hiding this comment.
| 3. follow step 2. to 8. of the in ### 2. described instructions | |
| 3. follow step 2. to 8. of the instructions described in ### 2. |
|  | ||
|
|
||
| For those who do like to have written instructions: | ||
| 1. copy the repository link (see ### 1.) |
There was a problem hiding this comment.
regarding the "### 1.":
Chapters can be linked in Markdown, but without an IDE that auto-generates you the links it's quite a mess.
When we're done with everything else, I can add those links for you and show you next week how I did that using VS Code (which is by the way great for writing Markdown ;) )
Basti-iTAS-PLMS
left a comment
There was a problem hiding this comment.
Please wait until I added the references, before you merge this PR :)
Basti-iTAS-PLMS
left a comment
There was a problem hiding this comment.
Please revise changed before merging.
Please check the instruction!