Beginner's guide

• Agree with your teammates on one small problem to solve.
• Choose the smallest version you can demonstrate.
• Set up the tools below and confirm everyone can open the project.
• Save working progress often.

1. Create a GitHub account for sharing the project.
2. Install VS Code, an app for reading and editing code.
3. Install GitHub Desktop and sign in. This guide uses it instead of terminal commands.
4. In VS Code, install the Codex extension from OpenAI and sign in.
5. Clone your team's repository in GitHub Desktop, then open it in VS Code.

Clone means downloading a working copy of a shared project. If you use Linux or a managed Chromebook, ask an organizer or mentor for an approved setup.

Git tracks project changes, like a history you can return to. GitHub stores the shared online copy.

Repository

The project folder and its saved history, often called a "repo."

Commit

A named checkpoint containing a set of changes.

Branch

A separate work lane where you can change code safely.

Pull

Download your teammates' latest changes from GitHub.

Push

Upload your commits to GitHub.

1. Pull before you start so your copy is current.
2. Create a short, clearly named branch, such asadd-login-screen.
3. Make one small change and test it.
4. Review the changed files in GitHub Desktop.
5. Write a clear commit message, such asAdd login form, and commit.
6. Push the branch and tell your team it is ready.
7. Ask whether to open a pull request, which is a request to review and merge your branch into the shared project.

Tell teammates which files you are editing. Amerge conflict means Git cannot combine overlapping changes. Do not delete anyone's work; ask a teammate or mentor to resolve it with you.

AI coding tools respond to normal-language instructions calledprompts. They can explain code, draft changes, investigate errors, and suggest tests. They can also be wrong, so treat their output as a draft.

Examples include Codex, GitHub Copilot, Cursor, and Claude Code. This guide uses Codex because it works beside your project in VS Code and shows changes for review.

Open your project folder in VS Code, then select the Codex icon. If it is hidden, open the Command Palette and runCodex: Open Codex Sidebar.

Start by asking Codex to explain, not edit:

Explain this project in beginner-friendly language. Do not change any files.

A useful prompt includes a goal, context, constraints, and verification.

Add a simple loading state to the results screen. Keep the change small, use the project's existing style, explain each changed file, and run the relevant checks.

For debugging, paste the exact error and describe what happened:

Explain this error in plain language. Identify the likely cause, propose one small fix, and tell me how to verify it.

Follow the same loop every time: ask, review the changes, run and test the project, then commit.

• Never paste passwords, API keys, personal data, or the contents of a .env file. A .env file commonly stores private settings and secrets.
• Read commands before approving them, especially commands that install or delete something.
• Check that suggested packages and APIs exist.
• Do not merge code your team cannot explain at a basic level.
• Follow the official De Anza Hacks rules for AI use and attribution. Specific event guidance is pending until organizers publish it.

1. Read the first error that explains what failed; later errors may be side effects.
2. Repeat the problem and review the most recent change.
3. Undo the smallest recent change if you need to return to a working state.
4. Ask for help with the exact error, what you expected, and what you already tried.

Getting help early is part of a hackathon. A teammate or mentor may spot quickly what is hard to see alone.

• Build the smallest version you can demonstrate before adding extras.
• Commit every working milestone and keep secrets out of GitHub.
• Add a README that explains the problem, solution, team, and setup steps.
• Test the project on another device or teammate's computer.
• Save backup screenshots or a short recording.
• Practice a one-minute demo and check the official submission requirements.

Devpost is the website De Anza Hacks uses to collect project submissions. Creating a Devpost account does not register you for the hackathon; use the official event page and choose Join hackathon when organizers share the link.

1. Choose one teammate to select Start project, then add every teammate to the submission.
2. Add the project name, a one-line summary, and a clear thumbnail.
3. Explain the problem, what the project does, how you built it, challenges, and what your team learned.
4. Add the tools you used, screenshots, and any required code, demo, or video links. Check that judges can open every link.
5. Read the event rules and complete any additional questions; requirements vary by hackathon.
6. Select Submit project before the deadline. A project marked Draft is not submitted, so check for the confirmation message and Submittedlabel.

Start the draft early. Devpost lets you update a submitted project until the deadline. The official De Anza Hacks Devpost link and deadline are pending organizer confirmation.

These videos are optional; all essential steps are written here.

• GitHub for Beginners: No Terminal Required!11:40 · Git, GitHub Desktop, commits, cloning, pushing, pulling, and undoing mistakes.
• OpenAI Codex in your code editorAbout 6 minutes · Exploring code, making changes, and reviewing the result.

• Set up GitHub Desktop
• Get started with VS Code
• Use the Codex IDE extension
• Submit a hackathon project on Devpost