Prerequisites

  1. Familiarity with Git basic line commands. Refer to the preprinted git cheat sheet that we have received previously (PDF version).
  2. Familiarity with Markdown formatting. Refer to the preprinted Markdown fold that we have received previously (PDF version).

Warnings

  1. Never use the GitHub website to upload your work. This will almost ruin the work of your teammates. You should only rely on the git commands.

  2. When you publish your changes, it may happen that one of your teammates has published some updates before you do, so you need to git pull origin master first. So never use as a solution: git push -f origin master (by adding -f) or git push --force origin master (by adding --force flag).

This is guaranteed to ruin and overwrite your teammates work.

git push origin master --force in practice:

$ git push --force origin master

$ git push --force origin master

Posted by NixCraft on Tuesday, 15 March 2016

Another practical git push origin master --force

Recommendations

You are expected to often execute git commands that access the remote repository:

  1. git clone url: which clones the remote repository for the first time.
  2. git pull origin master: which merges the updates on the remote repository (almost made by your teammates) into your local repository.
  3. git push origin master: that publishes your local updates to the remote repository.

Each of these commands requires providing your username and password. It becomes a cumbersome when you frequently make minor incremental changes. Follow these simple steps that guides you towards using public key authentication instead of the username and password.

Objectives

  • Collaborate as a group in a single repository.
  • Use the simple Markdown to annotate your document structure.

Deadline

Tuesday of 19 March 2019, 11:59 PM (PST time)

Assignment in Groups: Resume

Creating a Team or Joining an existing team

  • Know your team id from this sheet.
  • Join the assignment page from here. skip this first dialogue.
    • If you are the team leader, create a new team using the label SBE201-2021 Teamxx (e.g for team #1, SBE201-2021 Team01).
    • Otherwise, if you are not the team leader, find your team label as SBE201-2021 Teamxx, where xx is the group number in two digits, then join it. If you don’t find it then ask your team leader to register your team as described above.

Start working in your resume

  • After cloning your repository of your team, open the folder using Visual Studio Code, and work in your Markdown file.
  • The team should write their plain resumes in separate files. You should find 6 files, choose the one associated with order your name appeared this sheet.
  • Start drafting a basic resume of yours, you may use this file as a template.
  • You can find extra guidelines in the README.md file of your repository.
  • After finishing, add your name in the table in the README.md file.
  • A reference for GitHub emojis