Skip to content

Add files via upload #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gitsofaryan merged 6 commits into from
Oct 29, 2025
Merged

Add files via upload #42

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
cfeffe9
Add files via upload
Ayushgautam16 Oct 29, 2025
ef2a3c1
Todo webapp
Ayushgautam16 Oct 29, 2025
6021f90
Add files via upload
Ayushgautam16 Oct 29, 2025
ef84230
Add files via upload
Ayushgautam16 Oct 29, 2025
2b34087
Add files via upload
Ayushgautam16 Oct 29, 2025
f103d83
Godseye
Ayushgautam16 Oct 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 22 additions & 23 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,22 @@
# Java
*.class
*.log
*.jar
*.war
*.ear
# Build directories
target/
build/
out/
bin/
# Editor temporary files
*.swp
*~
# IDE files
.idea/
.vscode/
*.iml
*.iws
*.ipr
# Other
.DS_Store
Thumbs.db
# Python
__pycache__/
*.py[cod]
*.egg-info/
.venv/
venv/
env/

# OS
.DS_Store

# IDE
.vscode/
.idea/

# Env
.env

# Caches
.pytest_cache/
.mypy_cache/

154 changes: 154 additions & 0 deletions DEPLOYMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,154 @@
# 🚀 GitHub Pages Deployment Guide

This guide will walk you through deploying your Singly Linked List Game to GitHub Pages.

## Prerequisites

- A GitHub account
- Git installed on your computer
- Basic knowledge of Git commands

## Step-by-Step Deployment

### 1. Create a New Repository

1. Go to [GitHub](https://github.com) and sign in
2. Click the "+" icon in the top right corner
3. Select "New repository"
4. Name your repository (e.g., `singly-linked-list-game`)
5. Make it **Public** (required for free GitHub Pages)
6. Don't initialize with README (we already have one)
7. Click "Create repository"

### 2. Upload Your Files

#### Option A: Using GitHub Web Interface
1. In your new repository, click "uploading an existing file"
2. Drag and drop all your project files:
- `index.html`
- `styles.css`
- `script.js`
- `README.md`
- `.gitignore`
3. Add a commit message: "Initial commit: Singly Linked List Game"
4. Click "Commit changes"

#### Option B: Using Git Command Line
```bash
# Clone the repository
git clone https://github.com/yourusername/singly-linked-list-game.git
cd singly-linked-list-game

# Copy your project files to this directory
# (index.html, styles.css, script.js, README.md, .gitignore)

# Add all files
git add .

# Commit
git commit -m "Initial commit: Singly Linked List Game"

# Push to GitHub
git push origin main
```

### 3. Enable GitHub Pages

1. Go to your repository on GitHub
2. Click on **Settings** tab
3. Scroll down to **Pages** section (or click "Pages" in the left sidebar)
4. Under **Source**, select "Deploy from a branch"
5. Under **Branch**, select `main` (or `master`)
6. Click **Save**

### 4. Wait for Deployment

- GitHub will automatically build and deploy your site
- This usually takes 1-5 minutes
- You'll see a green checkmark when deployment is complete

### 5. Access Your Game

Your game will be available at:
```
https://yourusername.github.io/singly-linked-list-game
```

## 🎯 Custom Domain (Optional)

If you want to use a custom domain:

1. In the Pages settings, enter your domain in the "Custom domain" field
2. Add a CNAME record in your domain provider's DNS settings
3. Point it to `yourusername.github.io`

## 🔄 Updating Your Game

To update your game after making changes:

### Using GitHub Web Interface
1. Navigate to the file you want to edit
2. Click the pencil icon to edit
3. Make your changes
4. Commit with a descriptive message

### Using Git Command Line
```bash
# Pull latest changes
git pull origin main

# Make your changes to files

# Add and commit
git add .
git commit -m "Update: [describe your changes]"

# Push to GitHub
git push origin main
```

## 🐛 Troubleshooting

### Common Issues

**Page not loading:**
- Check if the repository is public
- Verify all files are in the root directory
- Wait a few minutes for deployment to complete

**Game not working:**
- Check browser console for JavaScript errors
- Ensure all file paths are correct
- Verify all files were uploaded

**Styling issues:**
- Check if CSS file was uploaded correctly
- Verify file names match exactly (case-sensitive)

### Getting Help

- Check the [GitHub Pages documentation](https://pages.github.com/)
- Look for error messages in the Actions tab
- Verify your repository settings

## 📱 Testing

After deployment, test your game on:
- Desktop browsers (Chrome, Firefox, Safari, Edge)
- Mobile devices
- Different screen sizes
- Various browsers

## 🎉 Success!

Once deployed, you can:
- Share your game with friends and students
- Use it in educational settings
- Showcase your programming skills
- Contribute to open source education

---

**Happy Deploying! 🚀**

Comment on lines +1 to +153
Copy link

@coderabbitai coderabbitai bot Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major

🧩 Analysis chain

Documentation quality is good, but verify repository context.

The deployment guide is well-written and comprehensive. However, this documentation assumes the repository is dedicated to the Singly Linked List Game, while the PR is targeting a repository named "Hacktoberfest-Projects-2025". This suggests a potential mismatch in project scope or repository purpose.

Additionally, the PR description mentions an image upload (![Uploading Nitro_Wallpaper_03_3840x2400.jpg…]()), but the actual changes introduce a complete game project. Please clarify the intended purpose of this PR.

I need to verify the repository context to confirm the concerns raised. Let me investigate the PR and repository structure.

🏁 Script executed:

#!/bin/bash
# Check repository name and structure
echo "=== Repository information ==="
if [ -f "README.md" ]; then
  head -20 README.md
fi

echo -e "\n=== Files in root directory ==="
ls -la | head -30

echo -e "\n=== Check for existing project directories ==="
fd -d 1 -t d

Length of output: 3177

🏁 Script executed:

#!/bin/bash
# Look for PR/PR context files and existing structure
echo "=== Check for .github/workflows ==="
if [ -d ".github/workflows" ]; then
  ls -la .github/workflows/
fi

echo -e "\n=== Check PR information via git ==="
git log -1 --format="%B" 2>/dev/null || echo "Git history not available"

echo -e "\n=== Search for all markdown files ==="
fd -e md

Length of output: 552

🏁 Script executed:

#!/bin/bash
# Check if there are game-related files being added
echo "=== Look for HTML/CSS/JS game files ==="
fd -e html -e js -e css | head -20

echo -e "\n=== Check git status for new files ==="
git status --short 2>/dev/null || echo "Git status not available"

echo -e "\n=== Check for image files ==="
fd -e jpg -e png -e gif | head -20

Length of output: 898

Let me check the git history to determine if DEPLOYMENT.md is a new addition or pre-existing.

🏁 Script executed:

#!/bin/bash
# Check git history for DEPLOYMENT.md and when it was added
echo "=== Git history for DEPLOYMENT.md ==="
git log --oneline --all -- DEPLOYMENT.md 2>/dev/null | head -10

echo -e "\n=== Git history for root README.md ==="
git log --oneline --all -- README.md 2>/dev/null | head -10

echo -e "\n=== Check git diff for current branch ==="
git diff --name-only HEAD~1 2>/dev/null || echo "No previous commit"

echo -e "\n=== Check if DEPLOYMENT.md is new in current branch ==="
git show HEAD:DEPLOYMENT.md &>/dev/null && echo "DEPLOYMENT.md exists in HEAD" || echo "DEPLOYMENT.md is new"

Length of output: 619

🏁 Script executed:

#!/bin/bash
# Check if there's an existing subdirectory structure for the game
echo "=== Check for 'singly-linked-list' or 'game' directories ==="
fd -t d -i "singly|linked|list|game" | head -20

echo -e "\n=== List all top-level directories with projects ==="
ls -d */ 2>/dev/null | sort

echo -e "\n=== Check root-level README content length and focus ==="
wc -l README.md
grep -E "^#" README.md | head -5

Length of output: 569

Move game project files into a subdirectory to match repository structure.

This PR adds a complete game project to the repository root, but the established pattern throughout this Hacktoberfest repository places each project in its own subdirectory (e.g., Tic-Tac-Toe/, rock-paper-scissors/, Hand-Written-Digit-Recognition/).

Currently, DEPLOYMENT.md, index.html, script.js, styles.css, and a game-specific README.md are placed at the root level, which:

  • Pollutes the repository root
  • Breaks the existing organizational pattern
  • Makes the root README game-specific rather than repository-level

Move all game files (including DEPLOYMENT.md) into a dedicated subdirectory such as Singly-Linked-List-Game/ to maintain consistency with other projects in the repository.

🧰 Tools
🪛 LanguageTool

[style] ~90-~90: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... Interface

  1. Navigate to the file you want to edit
  2. Click the pencil icon to edit
    ...

(REP_WANT_TO_VB)

[grammar] ~148-~148: Use a hyphen to join words.
Context: ...programming skills

  • Contribute to open source education

**Happy Deplo...

(QB_NEW_EN_HYPHEN)

🪛 markdownlint-cli2 (0.18.1)

73-73: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

152-152: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🤖 Prompt for AI Agents 
In DEPLOYMENT.md lines 1-153: the entire game (DEPLOYMENT.md, index.html,
script.js, styles.css, README.md, etc.) is currently in the repository root
which breaks the project's per-folder organization; create a new directory named
Singly-Linked-List-Game/ and move all game files (DEPLOYMENT.md and the game's
HTML/CSS/JS/README/.gitignore) into that folder, update any internal relative
paths and the GitHub Pages URL in DEPLOYMENT.md to reflect the new path
(https://yourusername.github.io/Singly-Linked-List-Game), and ensure the
repository root README remains generic (optionally add a link to the new
subdirectory).

Your Singly Linked List Game will be live on the web and accessible to anyone with an internet connection!
23 changes: 23 additions & 0 deletions LICENSE
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
MIT License

Copyright (c) 2025

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.


134 changes: 46 additions & 88 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,88 +1,46 @@
# Hacktoberfest Projects Repository

Welcome to the **Hacktoberfest Projects** repository! This is a place where developers can upload and showcase their full stack projects. Whether you're an experienced developer or just starting, feel free to contribute your projects and help others learn.

## Table of Contents

- [About the Repository](#about-the-repository)
- [How to Get Started](#how-to-get-started)
- [How to Contribute](#how-to-contribute)
- [Past Contributors](#contributors)
- [License](#license)

## About the Repository

This repository collects full stack projects using popular technologies like:

- **Frontend**: HTML, CSS, JavaScript, React, Angular, Vue.js, etc.
- **Backend**: PHP, Go, Node.js, Express, Django, etc.
- **Databases**: MongoDB, PostgreSQL, MySQL, etc.

Each project is designed to be easy to set up and customize, offering a great resource for developers of all levels.

## How to Get Started

Follow these steps to start using this repository:

1. **Clone the repository**

```bash
git clone https://github.com/gitsofaryan/Hacktoberfest-Projects-2024.git
cd Hacktoberfest-Projects-2024

2. Explore projects: Look through the folders to find projects that interest you.

3. Run a project: Each project has a README file with instructions on how to set it up and run.


## How to Contribute
We welcome your contributions! Here’s how to add your project to the repository:

### Steps to Contribute

1. Fork the repository: Click the "Fork" button at the top of the page.

2. Create a new branch for your project:

```bash
git checkout -b your-project-name
```

3. Add your project: Create a new folder for your project and include:

- Your source code
- A README file with instructions for setup and running the project
- Any other important files (e.g., images, config files)

4. Commit your changes:

```bash
git add .
git commit -m "Added my project: Your Project Name"
```

5. Push to your branch:
```bash
git push origin your-project-name
```

6. Create a Pull Request: Go back to the original repository and click "New Pull Request."

## Pull Request Guidelines

- Make sure your README clearly explains how to set up and run your project.
- Follow best coding practices.
- Provide a brief description of your project in the Pull Request.

[![Contributors](https://img.shields.io/github/contributors/gitsofaryan/Hacktoberfest-Projects-2025?style=for-the-badge)](https://github.com/gitsofaryan/Hacktoberfest-Projects-2025/graphs/contributors)

<!-- Contributors avatars (auto-updating) -->
<p align="left">
<a href="https://github.com/gitsofaryan/Hacktoberfest-Projects-2025/graphs/contributors">
<img src="https://contrib.rocks/image?repo=gitsofaryan/Hacktoberfest-Projects-2025" alt="Contributors" />
</a>
</p>

See the full list of contributors and their contributions on the [`GitHub Contributors Graph`](https://github.com/gitsofaryan/Hacktoberfest-Projects-2025/graphs/contributors).

### Thank you for contributing to the Hacktoberfest Projects repository! We’re excited to see your projects and hope this helps you grow as a developer. Happy coding!
## Godseye OSINT Toolkit (MVP)

Godseye is a privacy-respecting, public-data OSINT toolkit. It aggregates open sources like crt.sh (certificate transparency), Wayback Machine, and GitHub to help investigate domains and usernames.

### Features (MVP)
- Domain enrichment: subdomains via crt.sh, historical URLs via Wayback Machine
- Username enrichment: presence checks on popular platforms + GitHub profile summary
- HTTP API (FastAPI) and CLI (Typer)

### Quickstart

1) Python 3.10+

2) Create a virtual environment and install deps
```bash
python -m venv .venv
. .venv/Scripts/activate # Windows PowerShell: . .venv/Scripts/Activate.ps1
pip install -r requirements.txt
```

3) (Optional) Configure environment variables
Copy `.env.example` to `.env` and add tokens if you have them.

4) Run the CLI
```bash
python -m godseye.cli domain example.com
python -m godseye.cli username torvalds
```

5) Run the API
```bash
uvicorn godseye.api.main:app --reload
# Open: http://127.0.0.1:8000/docs
```

### Environment variables
- `GITHUB_TOKEN` (optional): increases GitHub rate limits for user lookups.

### Notes
- Only public sources are used. Respect rate limits and each source's ToS.
- Results are best-effort and may contain inaccuracies. Always verify critical findings.

### License
MIT


Loading
Loading