Hackathon Submission Guidelines

Submission Deadline

Date and Time: Submissions must be completed by 4:45 PM, 28 December 2024.

This includes both code submission and any deployment.

Late submissions will not be accepted under any circumstances. Plan ahead to avoid last-minute issues.

Submission Process

1. Google Forms Submission:
   • You will receive a Google Forms link to submit the following details:
   • Team ID
   • GitHub repository link (must be public and follow the monorepository structure).
   • Git commit hash for the specific commit you want to be evaluated.
   • A commit hash is a unique identifier for your changes in Git.
   • We will evaluate your submission based only on the code and deployment associated with this commit hash.
2. Deployment (if applicable):
   • If you are deploying your project, the deployment must also be completed by 4:45 PM, 28 December 2024.
   • In the Github README.md and description, provide the URL to your deployed application.
   • We will verify that the deployment matches the specified commit hash.

Repository Requirements

1. Monorepository Structure:
   • Your repository must contain both front-end and back-end code (if applicable) in a single repository.
   • Ensure the repository is well-organized for easy navigation.
2. No Bloated Repositories:
   • Exclude unnecessary files using .gitignore, such as:
   • node_modules (for Node.js projects)
   • .pyc or __pycache__ files (for Python projects)
   • Compiled binaries or any other language-specific package files.
3. Readme File:
   • Your repository must include a README.md file at the root, containing:
   • A brief description of your project.
   • The project structure.
   • Technologies and frameworks used.
   • Setup and run instructions.
   • Deployment links (if applicable)
   • Deployment details/steps documented (if applicable)
   • Documented features: Clearly list the requirements you implemented in detail.
4. Commit Hash Specifics:
   • A commit hash is a unique identifier for a specific set of changes in Git.
   • To find your commit hash:
   • Run git log in your terminal to view your commit history.
   • Copy the hash (e.g., e3c45f1d...) of the commit you want us to evaluate.

Important:

After submission, you must not push any changes to your repository.

Any mismatch between the deployment and the specified commit hash will lead to disqualification.

Key Notes

1. No Extensions:
   • The deadline applies to both code and deployment. Plan your submission accordingly.
2. Deployment Verification:
   • We will manually verify that the deployment matches the code in the specified commit hash.
3. Beginner-Friendly Support:
   • If you're unfamiliar with Git or commit hashes, refer to Git Basics Guide.
4. Evaluation Criteria:
   • Only documented and clearly explained features will be evaluated.
   • If you fail to document a feature, you will not receive points for it.

Recommendations

• Submit early to avoid last-minute issues.
• Double-check your repository for unnecessary files.
• Ensure your deployment is live and matches your commit hash.
• Clearly document all implemented features in your README.md.

By adhering to these guidelines, you help ensure a smooth evaluation process. Good luck!