...

Commits (2)
This diff is collapsed.
 \documentclass{article} \documentclass{article} \usepackage[hidelinks]{hyperref} \providecommand{\handoutsTitle }{\vspace{0.5cm}Practical 1 \\ \vspace{0.5cm}Groups, Projects, and File Handling} \providecommand{\handoutsTitle }{\vspace{0.5cm}Practical 1 \\ \vspace{0.5cm}Groups, Projects, and File Handling} \usepackage{handouts} \input{../shared/shared} \usepackage{handouts} \input{../shared/shared} \begin{document} \makeHeader \begin{document} \makeHeader \subsubsection*{GitLab Access} Open \url{https://git.lumc.nl} in your browser. \medskip Open \url{https://git.lumc.nl} in your browser. \medskip If you have an LUMC account, make sure that the \textbf{LDAP} authentication mode is selected. Next, introduce your \textbf{LUMC username} and \textbf{password} in the authentication form. If you have an LUMC account, make sure that the \textbf{LDAP} authentication mode is selected. Next, introduce your \textbf{LUMC username} and \textbf{password} in the authentication form. \medskip If you do not have an LUMC account, make sure that the \textbf{Standard} authentication mode is selected. Next, introduce your provided \textbf{username} and \textbf{password} in the authentication form. If you do not have an LUMC account, make sure that the \textbf{Standard} authentication mode is selected. Next, introduce your provided \textbf{username} and \textbf{password} in the authentication form. \medskip You can now edit your profile by clicking on the \textbf{Settings}'' item option present on the top right menu. You can now edit your profile by clicking on the \textbf{Settings}'' item option present on the top right menu. \subsubsection*{Explore the Demo Project} ... ... @@ -33,39 +39,49 @@ Navigate to the demo project page and browse its contents:\\ \subsubsection*{Group Creation} Create a new \textbf{group} that has the visibility level set to \textbf{Private}''. Create a new \textbf{group} that has the visibility level set to \textbf{Private}''. \medskip Add one of your neighbours, e.g. left neighbour, to the group as \textbf{Guest}''. At the same time, make sure that you are as well added to one of your colleagues project as a \textbf{Guest}''. Add one of your neighbours, e.g. left neighbour, to the group as \textbf{Guest}''. At the same time, make sure that you are as well added to one of your colleagues project as a \textbf{Guest}''. \medskip Change your neighbour role within the group to \textbf{Master}''. Change your neighbour role within the group to \textbf{Maintainer}''. \medskip Check your email to see the GitLab notifications. \subsubsection*{Project Creation} Create a new \textbf{project}, under your newly created group, which has the visibility level set to \textbf{Private}''. Create a new \textbf{project}, under your newly created group, which has the visibility level set to \textbf{Private}''. \medskip Add a different neighbour, e.g. right neighbour, as \textbf{Developer}'' for the new project. At the same time, make sure that you are as well added to one of your colleagues project as a \textbf{Developer}''. Add a different neighbour, e.g. right neighbour, as \textbf{Developer}'' for the new project. At the same time, make sure that you are as well added to one of your colleagues project as a \textbf{Developer}''. \medskip Change the role of the \textbf{Developer}'' neighbour within the project to \textbf{Master}''. Change the role of the \textbf{Developer}'' neighbour within the project to \textbf{Maintainer}''. \medskip Check your email to see the GitLab notifications. \subsubsection*{File Handling} Create a \textbf{README.md} file in your newly created project and add the project title in it. Create a \textbf{README.md} file in your newly created project and add the project title in it. \medskip Check the project main page and note that the description in the README.md file appears on this page. Check the project main page and note that the description in the README.md file appears on this page. \medskip \textbf{Edit} the README.md file and add a bit more description in it below the project title. Write a very brief sumary in the commit message text box. \textbf{Edit} the README.md file and add a bit more description in it below the project title. Write a very brief sumary in the commit message text box. \medskip Go to the \textbf{history} page of the README.md file and check the differences. ... ...
 \documentclass{article} \documentclass{article} \providecommand{\handoutsTitle }{\vspace{0.5cm}Practical 2 \\ \vspace{0.5cm}Issues, Labels, Milestones, and The Issue Board} \providecommand{\handoutsTitle }{\vspace{0.5cm}Practical 2 \\ \vspace{0.5cm}Issues, Labels, Milestones, and The Issue Board} \usepackage[usenames,dvipsnames,svgnames,table]{xcolor} \usepackage{handouts} \input{../shared/shared} \usepackage{handouts} \input{../shared/shared} \begin{document} \makeHeader \begin{document} \makeHeader \subsubsection*{Issue Creation} Navigate to the project in which you are the \textbf{Owner}''. \medskip Create a new \textbf{issue} in which the neighbour with \textbf{Master}'' \textbf{group role} is asked to add a new folder (directory) named \textbf{data}'' together with a \textbf{README.md}'' file in it. Create a new \textbf{issue} in which the neighbour with \textbf{Maintainer}'' \textbf{group role} is asked to add a new folder (directory) named \textbf{data}'' together with a \textbf{README.md}'' file in it. \medskip Check your email and GitLab \textbf{To Do}'' page for the notifications. \medskip Navigate to the \textbf{issue} that was assigned to you. Add a folder entitled \textbf{data}'' to that project.% (you have to reach the \textbf{repository section} of the project, press the \textbf{+}'' button, and select \textbf{directory}''). Navigate to the \textbf{issue} that was assigned to you. Add a folder entitled \textbf{data}'' to that project. \medskip Add a \textbf{README.md}'' file under the newly created \textbf{data}'' folder. Mention in the content that it is intended for data results. Add a \textbf{README.md}'' file under the newly created \textbf{data}'' folder. Mention in the content that it is intended for data results. \medskip \textbf{Comment and close} the issue that was assigned to you. ... ... @@ -34,52 +39,67 @@ Add a \textbf{README.md}'' file under the newly created \textbf{data}'' fold Navigate to the project for which you are the \textbf{Owner}''. \medskip Create the following \textbf{labels}: \textit{\color{Emerald}{File handling}}, \textit{\color{Sepia}{Description}}, \textit{\color{ForestGreen}{Wiki}}, \textit{\color{BurntOrange}{Started}}, and Create the following \textbf{labels}: \textit{\color{Emerald}{File handling}}, \textit{\color{Sepia}{Description}}, \textit{\color{ForestGreen}{Wiki}}, \textit{\color{BurntOrange}{Started}}, and \textit{\color{Violet}{Advanced}}. Make sure that you use different colors. \medskip Navigate to the closed issue and \textbf{assign the \textit{\color{Emerald}{File handling}} label} to it.% (use the issue $<<$ menu on the right: go to \textbf{Labels Edit}'', click on the corresponding label, press the \textbf{x}'' button, and refresh (F5) the page). Navigate to the closed issue and \textbf{assign the \textit{\color{Emerald}{File handling}} label} to it. \subsubsection*{Milestone Creation} Make sure you are under the project for which you are the \textbf{Owner}''. \medskip Create a new \textbf{milestone} entitled \textbf{Complete description and wiki}''. Create a new \textbf{milestone} entitled \textbf{Complete description and wiki}''. \subsubsection*{Basic Issue Manipulation} Create a new \textbf{issue} entitled \textbf{Describe the project}'' under the new \textbf{milestone}. Make sure that the \textbf{\textit{\color{Sepia}{Description}}} label is attached to it and that there is \textbf{no assignee}. Create a new \textbf{issue} entitled \textbf{Describe the project}'' under the new \textbf{milestone}. Make sure that the \textbf{\textit{\color{Sepia}{Description}}} label is attached to it and that there is \textbf{no assignee}. \medskip \textbf{Comment} on the issue that it is too broad and that it should be split into smaller issues. \textbf{Comment} on the issue that it is too broad and that it should be split into smaller issues. \medskip Change the title of the \textbf{Describe the project}'' issue to \textbf{Finish main README.md}''. Change the title of the \textbf{Describe the project}'' issue to \textbf{Finish main README.md}''. \medskip Create another \textbf{issue} entitled \textbf{Make wiki page}'' under the \textbf{Complete description and wiki}'' milestone. Make sure that the \textbf{\textit{\color{Sepia}{Description}}} and \textbf{\textit{\color{ForestGreen}{Wiki}}} labels are attached to it and that there is no assignee. Create another \textbf{issue} entitled \textbf{Make wiki page}'' under the \textbf{Complete description and wiki}'' milestone. Make sure that the \textbf{\textit{\color{Sepia}{Description}}} and \textbf{\textit{\color{ForestGreen}{Wiki}}} labels are attached to it and that there is no assignee. \subsubsection*{Milestone Summary} Navigate to the \textbf{Complete description and wiki}'' milestone page and check its summary. Navigate to the \textbf{Complete description and wiki}'' milestone page and check its summary. \medskip %Drag the \textbf{Make wiki page}'' issue from the \textbf{Unstarted Issues (open and unassigned)}'' to the \textbf{Ongoing Issues (open and assigned)}''. Note that this assigns the issue to you. Click on the \textbf{Make wiki page}'' issue to go to its main page. Assign this issue to you. Click on the \textbf{Make wiki page}'' issue to go to its main page. Assign this issue to you. \subsubsection*{The Issue Board} Navigate to the issue board page of the project. \medskip Create two new \textbf{lists} by making use of the \textbf{\textit{\color{BurntOrange}{Started}}} and \textbf{\textit{\color{Violet}{Advanced}}} labels. Create two new \textbf{lists} by making use of the \textbf{\textit{\color{BurntOrange}{Started}}} and \textbf{\textit{\color{Violet}{Advanced}}} labels. \medskip Add the \textbf{Finish main README.md}'' issue to the board under the \textbf{Started}'' list. Add the \textbf{Finish main README.md}'' issue to the board under the \textbf{Started}'' list. \medskip \end{document} ... ...
 \documentclass{article} \documentclass{article} \providecommand{\handoutsTitle }{\vspace{0.5cm}Practical 3 \\ \vspace{0.5cm}Wiki and Markdown} \providecommand{\handoutsTitle }{\vspace{0.5cm}Practical 3 \\ \vspace{0.5cm}Wiki and Markdown} \usepackage{handouts} \input{../shared/shared} \usepackage{handouts} \input{../shared/shared} \begin{document} \makeHeader \begin{document} \makeHeader \subsubsection*{Wiki Page Creation} Navigate to the \textbf{Wiki section} of the project for which you are the \textbf{Owner}''. Navigate to the \textbf{Wiki section} of the project for which you are the \textbf{Owner}''. \medskip Add some content to the main page. A simple Welcome to the wiki of this project.'' text is enough. Add some content to the main page. A simple Welcome to the wiki of this project.'' text is enough. \medskip Create a new \textbf{wiki} page named \textbf{project-details}'' and enter some short content text. Make sure to mention somewhere the \textbf{project title}. Create a new \textbf{wiki} page named \textbf{project-details}'' and enter some short content text. Make sure to mention somewhere the \textbf{project title}. \medskip Navigate to the \textbf{issue board} page. Add the \textbf{Make wiki pages}'' issue to the issue board under the \textbf{Started}'' list. Navigate to the \textbf{issue board} page. Add the \textbf{Make wiki pages}'' issue to the issue board under the \textbf{Started}'' list. \medskip ... ... @@ -31,20 +37,26 @@ Go to edit the wiki \textbf{project-details}'' page and: \item Add a heading \textbf{Project members}''. \item Add a \textbf{list} with all the project members. \item Emphasis the project \textbf{Owner}''. \item \textbf{Link} the project title with the project page, i.e.,\\ \textit{https://git.lumc.nl/your-group-name/your-project-name}. \item \textbf{Link} the project title with the project page, i.e.,\\ \textit{https://git.lumc.nl/your-group-name/your-project-name}. \item Save and view the page. \end{itemize} Go to edit again the \textbf{project-details}'' wiki page and convert the members list into a three column \textbf{table} with the following column headings: \textbf{Name}, \textbf{GitLab project role}, \textbf{Short description}. Go to edit again the \textbf{project-details}'' wiki page and convert the members list into a three column \textbf{table} with the following column headings: \textbf{Name}, \textbf{GitLab project role}, \textbf{Short description}. \medskip Go to edit the \textbf{main (home) wiki page} and add a \textbf{link} to the project details wiki page (\textit{project-details}). Go to edit the \textbf{main (home) wiki page} and add a \textbf{link} to the project details wiki page (\textit{project-details}). \medskip Go to edit the \textbf{main README.md} file of the project and: Go to edit the \textbf{main README.md} file of the project and: \begin{itemize} \item Make the project title a \textbf{heading 1}. \item Add a link to the \textbf{project details wiki page}, i.e.,\\ \textit{https://git.lumc.nl/your-group-name/your-project-name/wikis/project-details}. \item Make the project title a \textbf{heading 1}. \item Add a link to the \textbf{project details wiki page}, i.e.,\\ \textit{https://git.lumc.nl/your-group-name/your-project-name/wikis/project-details}. \end{itemize} \subsubsection*{Again Issues and Milestones} ... ... @@ -52,10 +64,12 @@ Go to edit the \textbf{main README.md} file of the project and: Navigate to the \textbf{issue board} page. \medskip Drag the \textbf{Make wiki pages}'' and \textbf{Finish main README.md}'' issues to the \textbf{Done}'' list. Drag the \textbf{Make wiki pages}'' and \textbf{Finish main README.md}'' issues to the \textbf{Done}'' list. \medskip Navigate to the \textbf{Complete description and wiki}'' milestone page and check its summary. Navigate to the \textbf{Complete description and wiki}'' milestone page and check its summary. \medskip \end{document} ... ...