| ... | @@ -213,8 +213,8 @@ Tag your project for a deadline (a "tag" is a string which identifies a particul |
... | @@ -213,8 +213,8 @@ Tag your project for a deadline (a "tag" is a string which identifies a particul |
|
|
|
|
|
|
|
# Hints
|
|
# Hints
|
|
|
|
|
|
|
|
* Do not push unnecessary files! Add a `.gitignore` to your project. Always check that you do not send the numerical results of your code or the program binaries to GitLab. This is very important because it is not easy to remove files from the history stored on GitLab.
|
|
* Do not push unnecessary files! Add a `.gitignore` to your project. Always check that you do not send the numerical results of your code or the program binaries (executables) to GitLab. This is very important because it is not easy to remove files from the history stored on GitLab.
|
|
|
* Keep the `master` branch stable (it should always produce no errors during the build and all the tests should run successfully!).
|
|
* Keep the `master` branch stable (it should always produce no errors during the build and all the tests should run successfully!).
|
|
|
* Tell what you are currently doing to the other developers (using comments, issues, merge requests on GitLab... or by any other mean).
|
|
* Tell what you are currently doing to the other developers (using comments, issues, merge requests on GitLab... or by any other mean such as messenger, e-mails or, even better, face-to-face).
|
|
|
* Most of the previous commands are integrated into VS Code. You can easily see the modified files, prepare a commit or resolve conflicts (through the GUI, with your mouse!).
|
|
* Most of the previous commands are integrated into [VS Code](Visual Studio Code). You can easily see the modified files, prepare a commit or resolve conflicts (through the GUI, with your mouse!).
|
|
|
|
|
|