extras_handouts.tex 2.16 KB
Newer Older
Mihai's avatar
Mihai committed
1 2
\documentclass{article}

Mihai's avatar
Mihai committed
3
\providecommand{\handoutsTitle}{\vspace{0.5cm}GitLab and Markdown}
Mihai's avatar
Mihai committed
4 5 6 7 8 9 10 11

\usepackage{handouts}
\input{../shared/shared}

\begin{document}
\makeHeader

\subsubsection*{Collaboration}
Mihai's avatar
Mihai committed
12
In this practical, you'll work with both your repository and with the repository your neighbour created
Mihai's avatar
Mihai committed
13
during the previous practical. We'll refer to this repository as {\bf N}, and
Mihai's avatar
Mihai committed
14 15
to your own repository from the previous practical as {\bf Y}. Note that by now both repositories should have a 
corresponding GitLab project (a remote repository).
Mihai's avatar
Mihai committed
16 17
\bigskip

Mihai's avatar
Mihai committed
18
Make sure that your GitLab project \textbf{Y} is private and add your colleague as a member to it as \textbf{Guest}.
Mihai's avatar
Mihai committed
19 20
\bigskip

Mihai's avatar
Mihai committed
21
Try to \textbf{clone} his or her repository to your local machine. Make sure to do this in a separate directory.
Mihai's avatar
Mihai committed
22

Mihai's avatar
Mihai committed
23 24 25
\begin{itemize}
  \item \emph{Question:} Was the cloning successful? Try to identify why.
\end{itemize}
Mihai's avatar
Mihai committed
26

Mihai's avatar
Mihai committed
27
Change the role of your neighbour from \textbf{Guest} to \textbf{Developer} and try to \textbf{clone} his repository again once your neighbour made you a \textbf{Developer}.
Mihai's avatar
Mihai committed
28 29
\bigskip

Mihai's avatar
Mihai committed
30 31 32 33 34 35 36
Edit locally a file from your neighbour \textbf{N} directory, stage it, commit it, and try to \textbf{push}.

\begin{itemize}
  \item \emph{Question:} Were you able to push? Try to identify why.
\end{itemize}

Make an \textbf{issue} that you are not able to \textbf{push} and ask your role to be changed to \textbf{Master} in the project.
Mihai's avatar
Mihai committed
37 38 39
Assign the issue to your neighbour.
\bigskip

Mihai's avatar
Mihai committed
40
Navigate and check the issue that was assigned to you by your neighbour.
Mihai's avatar
Mihai committed
41 42
\bigskip

Mihai's avatar
Mihai committed
43 44 45 46 47 48
Change your neighbour's role in your GitLab project from \textbf{Developer} to \textbf{Master}.
\bigskip

After your neighbour upgraded your role to \textbf{Master} try to push again your changes to his GitLab repository.
\medskip

Mihai's avatar
Mihai committed
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
Comment and close the issue that was assigned to you.
\bigskip

Inspect the commit graph on GitLab.
\bigskip

\subsubsection*{Markdown}
Edit the README file in such a way that at least the following markdown features are used:
\begin{itemize}
 \item Multiple header levels.
 \item Emphasis: italics, bold, combined, underscores.
 \item Ordered and unordered lists.
 \item Tables.
 \item Links
\end{itemize}


\end{document}