It converts all .docx files into a more stable .txt format automatically.
It automatically backs up files to a USB drive every hour.
It provides a detailed, auditable history of every change, including who made it, when, and why, preventing confusion over which version is the 'source of truth'.
It encrypts all lab protocols, making them inaccessible to anyone outside the lab.
It is the software on your computer used to visually manage files and changes.
It is a tool for analysing experimental data and generating graphs.
It is a text editor specifically designed for writing scientific protocols.
It is the central, cloud-based 'remote' repository that stores the master copy of your lab's projects and serves as a backup.
automatically check for spelling errors in your protocols.
permanently delete files you no longer need.
hide files from your collaborators.
select which specific file changes you want to include in your next 'snapshot' or commit.
Fixed it
FEAT: Increase PCR annealing temp to 62°C for primer B
Changed the numbers on line 45 of the PCR SOP document as requested by Dr. Smith in our meeting about the failed experiment from last Tuesday.
Update protocol
When you need to share a file with someone who does not use Git.
Every time you save a file.
When you want to test a significant change to a protocol without affecting the stable, main version.
Only when the Principal Investigator gives you direct permission.
It saves a snapshot (a commit) of your work onto your local computer only.
It uploads all your committed local changes to the remote repository on Bitbucket, making them available to your colleagues.
It discards all the changes you have made since your last commit.
It downloads the latest changes from the Bitbucket repository to your local computer.
False
True
Push your current work.
Commit your own files immediately.
Perform a 'Pull' operation to download their updates to your local repository.
Create a new branch.
To create a permanent backup of your branch.
To force your changes into the main branch without anyone's approval.
To formally ask a colleague or PI to review your changes before they are merged into a main protocol.
To download files from the remote repository.
you and a colleague have independently changed the exact same line(s) of the same file, and Git doesn't know which version to keep.
you forget to write a commit message.
you try to commit a very large file, like a microscope image.
two people create branches with the exact same name.
A pull request
A tag
A commit message
A branch
All done? Get your grade