Difference between revisions of "Git-hub"

From hf.multiling
Jump to: navigation, search
(Public Experiments)
(Private Experiments)
Line 18: Line 18:
 
=== Private Experiments ===
 
=== Private Experiments ===
 
Remember that even if an experiment is considered private and requires membership to read, the Github is still not considered suitable storage for sensitive data. Do not include logs or personal information in the repository.
 
Remember that even if an experiment is considered private and requires membership to read, the Github is still not considered suitable storage for sensitive data. Do not include logs or personal information in the repository.
 +
 +
=== Working with Git ===
 +
There are more tutorials about working with Git than you can shake a branch at. You can use the web page for most normal use and some of us will choose to use the command line. But for most of us, it probably helps to have a graphical user interface. On the lab github web page, you can choose to download a repository using the green button labeled Code.
 +
 +
(Code)
 +
 +
As you can see from this image, you can download the repository as a zip file, but we want to download and install GitHub Desktop. Afterwards you will be asked to log in to GitHub, but that is the public GitHub and we can skip that step. Instead we choose a short name which will indicate who we are and an email address who will get the blame when someone flags our code as buggy. In the Multiling repository, it is probably a good idea to use the UiO user name and email.
 +
 +
==== Creating a new repository ====
 +
If you have new code that should be moved to our repository you would need to have a repository created for you, which you can then later be assigned write permissions to.

Revision as of 13:20, 24 March 2021



The lab has a Github area where projects can make repositories for their code on https://github.uio.no/hf-multiling-lab

While the landing page should be readable for "everyone" with a university computer account, each repository can have their own access levels. To access the main page you need to log on once using the link hf-multiling-lab. You will then have rudimentary access to some of the repositories and can browse them and download them, but not change them. Each user will then have to contact the lab management and ask to be granted access.

Access

Each experiment has its own repository. Access could the be granted to the project as a whole or on a per experiment basis. There are two ways to grant people access, namely giving access to the user on an individual basis or by adding the user to a github team. The lab management can create a team for a project group and afterwards the group can add (or revoke) members as need be. By adding a members to a team you can have a method to consistently granting people the correct access level.


Public Experiments

The repository is also meant to be a showcase for templates or code that should be available. When creating an experiment, please consider if you can create the experiment first in a generalized manner that can be such a showcase and hiding the specialized experiment.

There is currently no method in place to make the code published on the UiO github accessible to anyone outside the university.

Private Experiments

Remember that even if an experiment is considered private and requires membership to read, the Github is still not considered suitable storage for sensitive data. Do not include logs or personal information in the repository.

Working with Git

There are more tutorials about working with Git than you can shake a branch at. You can use the web page for most normal use and some of us will choose to use the command line. But for most of us, it probably helps to have a graphical user interface. On the lab github web page, you can choose to download a repository using the green button labeled Code.

(Code)

As you can see from this image, you can download the repository as a zip file, but we want to download and install GitHub Desktop. Afterwards you will be asked to log in to GitHub, but that is the public GitHub and we can skip that step. Instead we choose a short name which will indicate who we are and an email address who will get the blame when someone flags our code as buggy. In the Multiling repository, it is probably a good idea to use the UiO user name and email.

Creating a new repository

If you have new code that should be moved to our repository you would need to have a repository created for you, which you can then later be assigned write permissions to.