Learn · Certification · MuseHub

The history of the work

Pip slides a proposal to Sam while Ren waits
Pip opens a proposal, and Sam reviews the history of the work.

Pip opens a proposal, and Sam reviews the history of the work.

Muse is version control for multidimensional state, which means the history keeps the work as more than one flat file, so Sam can see what changed before he accepts it.

Ren is the colleague at the table, and he does not take the pen from Sam.

The client build later this week still waits on the history Sam accepts.

A person can init a repo, commit, branch, diff, merge, log, clone, fetch, and archive a snapshot.

Sam reads the difference between the proposal and the current work, then decides whether that change should become part of the history.

A branch keeps a line of work apart, a commit records a state, and a merge combines accepted work.

Sam compares the proposed change with the current work before deciding what enters the history.

The history of the work

Four questions. Each answer is a sentence from this lesson.

Sign up on Learn before this certificate can be emailed.

Start the course
  1. Who reviews the proposal?

    Who reviews the proposal?
  2. What does Muse keep for Sam?

    What does Muse keep for Sam?
  3. What is Sam checking before accepting the proposal?

    What is Sam checking before accepting the proposal?
  4. Which repo actions can a person take?

    Which repo actions can a person take?