Lab protocols for the Lowe-Power lab (scroll down for table of contents Readme)
Content was forked and from Mark Mandel/mjmlab. A lot of content was removed to streamline, but it’s not a bad idea to review it when we become more Git-competent.
lowepowerlab/protocols
as an exampleThis is a bit meta: a protocol to demonstrate how to contribute to the protocols. It also serves as a model for working with other lab repositories.
A repository (repo) in a directory or folder in which Git
is tracking changes. It is an effective method for version control and to collaborate on code and documents.
Git is the language that facilitates the change tracking and merging. GitHub is a git server and associated website that facilitates collaboration and posting online.
You can use Git on your own computer without the need for GitHub. However, since GitHub is a pretty and easy-to-use interface we will start there and then move to the command line Git interface on our computer.
See additional resources below to complete the following steps:
Recommendation is Visual Studio Code
VS Code
.Applications
folder on Mac).Code Spell Checker
, Excel Viewer
, GitHub Pull Requests
, Markdown Table Formatter
, Python
(helps check your code), etc.git config
on the command line (e.g., Terminal
app) and if it is not installed you will be prompted to install the XCode command line tools
, which includes Git
.Option 1: Follow the instructions on Mark Mandel’s Tutorial.
Option 2: If you want to frequently write & edit protocols, you can clone
the protocols repository into VS Code & push
changes to the master
from your computer/account.
search commands
dialog. Type “clone”, hit enter.Clone
the lab protocols github https://github.com/lowepowerlab/protocols. This will let you choose a local folder on your computer to view the lab protocols from.repo
in VS Code.Source Control
Menu (left). Add an informative description of the changes to the “Message”, such as “Fixed typos”, “Improved clarity”, “wrote protocol XXX”. Then commit
by clicking the checkmark. Verify your changes have registered on the master