<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">\textbf{Put a short PDF or text file called \texttt{submission&lt;X&gt;} into your git root directory and state all the points that you think you should get. This does not need to be long. Also mention the code files, where you implemented something if it is not obvious.}

To store or submit your code, please use our own, institute-hosted submission Gitlab \url{https://submission.cg.tuwien.ac.at}. 
You will receive a mail with your account and assignment repository as soon as they are ready.
The \texttt{master} branch is for development only.
You should push there while you are experimenting with the assignment and don't want to lose your work.
Once your solution works and you believe it is ready to be graded, please use the branch \texttt{submission&lt;X&gt;} where \texttt{&lt;X&gt;} is the assignment number. 
E.g., in order to submit your solution for the first assignment, push to \texttt{submission1}. 

If you push to a \texttt{submission} branch, the server will trigger automatic compilation and some testing for your code.
You can track the state of new submissions being processed on the GitLab page for your repository under "CI/CD &gt; Pipelines". 
If a stage fails, click on it to receive additional output and system information from the executing server.
If everything worked, you will shortly find a report with your test results in the "CI/CD" pipeline section, when checking the artifacts of the "report" stage. 
You can submit multiple times until the deadline, but don't clog the system by, e.g., using the submission server for debugging.
The last submission that was pushed before the deadline counts, regardless of the results from automatic testing. They are only meant for your convenience and to provide some automated feedback.

\textbf{Please make sure to NOT add unnecessary files (project folders, temporary compiler results), as your application will be created from your code and CMake setup only}. Examples of files that are usually relevant:
\begin{itemize}
	\item \textbf{changed or added} CMakeLists.txt files
	\item \textbf{changed or added} code files (.h, .cpp)
	\item \textbf{changed or added} test cases if you want to show off advanced solutions
\end{itemize}
Make sure to keep the directory structure in your submitted archive the same as in the framework.
</pre></body></html>