---
title: "Jam 01 - Summary to Submission"
tags:
- 3 🧪 in testing
- 4 🥳 done
- jam01
- git
- submission
created: 2025-01-20
updated: 2025-01-20
---
<!-- markdownlint-disable line-length single-h1 no-inline-html -->
<!-- markdownlint-configure-file { "ul-indent": { "indent": 4 }, "link-fragments": {"ignore_case": true} } -->

# Summary

{%hackmd dJZ5TulxSDKme-3fSY4Lbw %}

In this jam, you:

- Set up IntelliJ IDEA for Java development
- Created your first Java programs
- Learned about basic input/output
- Used proper code organization and documentation

# Project Structure

Your repository should now include:

jam01/
├── HelloWorld.java
├── CircleCalc.java

# Submission

## Final Repository Check

1. **Check Repository Status**

   git status

2. **Understand Your Status**
- If you see untracked files or changes:
- Are they source files that should be committed
- Are they changes to previously commited files?
- Should they already be ignored by .gitignore?
- Is your .gitignore in the right place and named correctly?
- A clean working tree is the goal - no uncommitted files should remain

3. **Take Action**
- Commit any remaining source files
- Commit any other changes files that should be saved
- Verify your .gitignore is working correctly but do not modify it unless you fully understand what those changes mean - accidentally ignoring assignment files could affect your grade!

4. **About Those .class Files**
- When you compiled from the command line, you might notice .class files in your directory
- Why don't these show up in `git status`? (Try researching this!)
- You can safely delete these files to keep your directory clean (but make sure you know why that is)

:::warning
🚧 **Repository Best Practices**

Your repository should always be in a clean state:

- All source code committed
- No build artifacts or IDE files tracked
- .gitignore properly configured
- Clear, descriptive commit messages

The template repository came with a proper .gitignore file. If you see ignored file types being tracked, check that your .gitignore is in the right place and named correctly.
:::

> 🔍 **Final Checkpoint**: Before finishing, verify:
>
> - `git status` shows a clean working tree
> - All source files are committed
> - No build artifacts or IDE files are tracked
> - Your commit messages clearly describe your changes