Skip to content

Latest commit

 

History

History
85 lines (60 loc) · 6.63 KB

README.md

File metadata and controls

85 lines (60 loc) · 6.63 KB
Raw

DEVELOPER STUDENT CLUBS TIET

Slack Bots

GitHub issues Code style: black GitHub repo size Dependabot Badge

Pre-commit License All Contributors

This repository contains various information retrieval bots for educational purposes. The bots are server and being currently used in DSC TIET Slack Channel and we serve the following information -

  • Information about various hackathons
  • Articles from Medium
  • Articles from Dev.to
  • Articles from Git Blogs

Basic Layout of the repository

  • Every folder in the repo represents the code of the bot which intends to scrape the file.
  • In that particular folder, you will find a README.md file, containing the instructions to run the project
  • Apart from that README will also consist of helping you support the hosting of your bots (as done by DSC TIET)

Contribution to the project

GitHub issues GitHub pull requests GitHub contributors

We follow a systematic Git Workflow -
  • Create a fork of this repo.
  • Clone your fork of your repo on your pc.
  • Add Upstream to your clone
  • Every change that you do, it has to be on a branch. Commits on master would directly be closed.
  • Make sure that before you create a new branch for new changes,syncing with upstream is neccesary.

Commits

  • Write clear meaningful git commit messages (Do read this).
  • Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (Check this for more info)
  • When you make very very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at here)
  • When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.

Note

  • If you are adding any new requirements for the project, make sure that you are adding it to requirements.txt
  • Use only yarn add package_name to add new packages to the frontend part.

Runtime Instructions

Contributors ✨

Thanks goes to these wonderful people for helping us with the project! :


Akshit Gupta
🚇 💻
Saurav-Shrivastav
🚇 💻
Ujjwal Agarwal
💻
Shubhank Saxena
🚧 🎨