Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

327 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Forktober GIF

PROJECT TITLE

Short description about the project. One or two lines that explain what it does and who it’s for.

made-by-acm


Table of Contents


About

Write a compelling overview about the project: the problem it solves, the motivation, and what makes it unique. Include a short roadmap or key features if helpful.


Quick Start

# 1) Fork and clone
# Click Fork on GitHub, then:
 git clone https://github.com/<your-username>/<repo>.git
 cd <repo>

# 2) Create a branch
 git checkout -b feat/your-feature

# 3) Install dependencies
# paste your install command(s) here

# 4) Run the project
# paste your run command(s) here

Usage

Provide examples and code snippets showing how to use the project. Add screenshots or GIFs if applicable.

# examples
<your-cli> init
<your-cli> run

Contributing

We welcome contributions of all kinds! Please read our Contributing Guidelines to get started quickly and make your PRs count.


Hacktoberfest

hactoberfest

Join us for Hacktoberfest! Quality > quantity.

  • Aim for meaningful, well‑scoped PR/MRs that solve real issues.
  • Non‑code contributions (docs, design, tutorials) are welcome via PR.
  • Full participation details: https://hacktoberfest.com/participation

Submitting a Pull Request

  1. Fork the repository (top‑right on GitHub)
  2. Clone your fork locally:
    git clone <HTTPS-ADDRESS>
    cd <NAME-OF-REPO>
  3. Create a new branch:
    git checkout -b <your-branch-name>
  4. Make your changes and stage them:
    git add .
  5. Commit your changes:
    git commit -m "feat: your message"
  6. Push to your fork:
    git push origin <your-branch-name>
  7. Open a Pull Request and clearly describe what you changed and why. Link related issues (e.g., “Fixes #123”).

Guidelines for Pull Request

  • Avoid PRs that are automated/scripted or plagiarized from someone else’s work.
  • Don’t spam; keep each PR focused and meaningful.
  • The project maintainer’s decision on PR validity is final.
  • For more, see our Contributing Guidelines and the Hacktoberfest participation rules.

Authors

Authors:
Contributors:


Community & Conduct

By participating in this project, you agree to abide by our Code of Conduct.


🤍 Crafted with love by ACM‑VIT

Footer GIF

About

No description, website, or topics provided.

Resources

Code of conduct

Contributing

Stars

4 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

Generated from ACM-VIT/template