Sweep: Replace GitHub webhook handling with GitLab equivalent

[sweep-ai[bot]]

PR Feedback (click)

• [ ] 👍 Sweep Did Well
• [ ] 👎 Sweep Needs Improvement

  Description

  This pull request updates our webhook handling mechanism to replace GitHub webhook processing with GitLab equivalents. It introduces changes in the probot/gitlab_app.js to handle merge_request events instead of issue events and securely store the accessToken. Additionally, it adds a new Flask app in sweepai/webhook_handler.py to process GitLab merge_request webhooks, post comments on merge requests, and handle potential errors.

Summary

• Modified probot/gitlab_app.js to:
  • Securely store the accessToken for GitLab API requests.
  • Change event handling from issue to merge_request, including posting a thank you note on merge requests.
• Added sweepai/webhook_handler.py Flask app to:
  • Handle incoming GitLab merge_request webhook events.
  • Post a predefined comment on the merge request using GitLab API.
  • Log the process and handle potential API errors.
• This update aligns our webhook processing with GitLab's ecosystem, enhancing our project's integration capabilities.

Fixes #81.

---

🎉 Latest improvements to Sweep:

• New dashboard launched for real-time tracking of Sweep issues, covering all stages from search to coding.
• Integration of OpenAI's latest Assistant API for more efficient and reliable code planning and editing, improving speed by 3x.
• Use the GitHub issues extension for creating Sweep issues directly from your editor.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

This is an automated message generated by Sweep AI.

[sweep-ai[bot]]

Rollback Files For Sweep

• [ ] Rollback changes to sweepai/utils/gitlab_utils.py
• [ ] Rollback changes to probot/gitlab_app.js
• [ ] Rollback changes to sweepai/webhook_handler.py

This is an automated message generated by Sweep AI.

[sweep-ai[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: We should use loguru for error logging. If the log is inside an exception, use logger.exception to add tracebacks, where logger is imported from loguru. Use f-strings for string formatting in logger calls (e.g. logger.info(f'Hello {name}') instead of logger.info('Hello {name}', name=name)).
• [ ] Apply: There should be no debug log or print statements in production code.
• [ ] Apply: All functions should have parameters and output annotated with type hints. Use list, tuple and dict instead of typing.List, typing.Tuple and typing.dict.
• [ ] Apply: Leftover TODOs in the code should be handled.
• [ ] Apply: All new business logic should have corresponding unit tests in the same directory. For example, sweepai/api_test.py tests sweepai/api.py. Use unittest and unittest.mock as required.
• [ ] Apply: Any clearly inefficient or repeated code should be optimized or refactored.
• [ ] Apply: Remove any comments before code that are obvious. For example # this prints hello world; print('hello world').

This is an automated message generated by Sweep AI.