♕ Chess GitHub Repository - softwareconstruction240/softwareconstruction GitHub Wiki

• 🖥️ Videos

In the following phases of the chess project you will add to, and enhance, the content you have created in a GitHub repository. The commit history that you establish through the course serves the following valuable purposes:

1. Backup - Every semester at least one student's computer dies. Having the ability to clone the repo to a new computer could save your grade in the course.
2. Portfolio - The code you develop in this course serves as a valuable portfolio artifact that you can use to demonstrate your mastery to future employers.
3. Proof of work - You can demonstrate your authorship of your code by consistently, and frequently, committing your work.
4. Exploration - The ability to create branches allows you to continuously experiment with different ideas without losing the main thread of your development. Likewise, you can try and implement something, realize it is not working and then simply reset to your last commit.
5. Experience - Git is the de facto versioning system. The experience you gain in this class will help prepare you for professional work.

All of this requires that you commit often. You should get in the habit of consistently making a small stable change and then committing.

1. Verify you have the latest code (git pull)
2. Refactor, test, and/or implement a small portion of cohesive code (test code test)
3. Commit and push (git commit git push)
4. Repeat

You will be most successful in this course if you set aside time each day, or every other day, to work on the project. Those consistent work sessions should be complemented with consistent commits. If you are not creating multiple commits every workday then you are not reflecting the code management practices you need in order to be successful in a production development environment.

For all of the above reasons, it is required that you use GitHub for your chess project. Additionally, you must use it consistently and frequently.

If you do not have the required number of commits, or if they are all clustered in a single burst of activity, then you will need to justify the discrepancy before the deliverable will be accepted.

1. Open your web browser to GitHub

2. Sign in to personal account, or create one if you don't already have a GitHub.com account. The GitHub Terms of Service allow only one account per individual.

3. View the chess template repository.

4. Use the template to create your own chess repository:

   1. Press "Use this template"

   2. Choose "Create a new Repository"

      

   3. Name it chess.

   4. Optionally, give it a meaningful description such as:

      Full-stack chess application built as a course project for BYU CS 240. It features a networked client-server architecture, with a command-line client, a server to manage users and games, and shared modules for implementing chess rules and game state management.

   5. Mark the repository as public so that it can be reviewed by the TAs and instructors. (This is the default.)

   6. Leave the box marked Include all branches unchecked. (This is the default.)

   7. Press "Create Repository"

      

5. Open a command line console window.

6. Clone the repository to your development environment. Make sure you put the clone of the repository in a directory that you use for this class's coursework. These commands will look something like the following.

   cd ~/byu/cs240
   git clone https://github.com/YOURACCOUNTHERE/chess.git
   cd chess

After you have cloned your repository locally, you need to make a change so that you can demonstrate that things are working properly.

1. Create a file in your repository directory named notes.md.
2. Add some content to it.
3. Add the notes.md file to the repo.
4. Commit the changes.
5. Push the changes to GitHub.

You can accomplish all of these changes with the following commands.

echo "# My notes" > notes.md
git add notes.md
git commit -am "initial(notes) creation"
git push

As you develop your chess application you should consider keeping notes about the techniques and technologies that you learn in the notes.md file that you have added.

Create your repository, clone it to your development environment, add the notes.md file, and push to GitHub.

Pass off the "GitHub Repository" assignment within the course auto-grading tool by selecting the assignment from the dropdown and clicking "Submit".

Before you can submit the assignment for grading, you will be asked to provide your GitHub repository URL. The URL should look something like this:

https://github.com/<youraccount>/chess

When you have successfully completed the assignment:

1. The AutoGrader will show a "Submission passed!" message and display your score.
2. Your score will be automatically entered in Canvas.
3. You will see a new item in your "Submission History" containing the notes generated during grading.
   • Click on the submission to view more details from grading
   • In future phases, you will see additional buttons to click for detailed compiler output.

• 🎥 Chess GitHub Repository (3:31) - [transcript]
• 🎥 Creating Chess GitHub Repository (4:34) - [transcript]