Skip to content

Latest commit

 

History

History
52 lines (38 loc) · 2.94 KB

README.md

File metadata and controls

52 lines (38 loc) · 2.94 KB

🤖 Gitty-Bot 🤖

Inspiration

  • Have you ever found yourself struggling to manage the issues and pull requests on your GitHub repository😟? Do you spend a lot of time manually adding labels to each issue or pull request😵? If yes, then with Gitty-Bot bot that can manage and add labels to issues and pull requests, you can save time and improve the overall organization of your repository.

How we built Gitty-Bot

  • We have used GitHub REST API Official documentation, and learnt how to make requests in GitHub Webhooks.
  • We have utilize Probot tool for configuring this app for GitHub.
  • We are using Replit for hosting all server, client and GitHub app.

What it does

Many things:

  • It can automatically respond to users on some events like opening the issue or opening the pull request.
  • Apply labels to the issue.
  • Listing Files on commenting the command in the pull request.
  • Assigning the issue on commenting the command in the issue or pull.
  • Sending message when pull or issue is closed based on the issue or pull state.
  • React on some good messages which have some good keywords.
  • Users can add custom messages to reply to the issues or pull requests.

Accomplishments that we're proud of

  • We got the new idea about how can we interact in GitHub through this bot.
  • We can now be able to explore it more, so as to automate the works in the repositories using this bot
  • Users can pre-define the custom messages which can help them to mark their identity with the help of Gitty-Bot

What we learned

  • We have learned the use of webhooks, to interact with GitHub
  • Use of probot to listen to the webhooks events and accomplishing the goals

What's next for Gitty-Bot

  • We are planning to explore and integrate machine learning algorithms that can be used to automate the whole flow of the repositories.

Problem ran into and Solution

Built With