Sweep: Replace Probot with GitLab App

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement

Description

This pull request represents a significant shift from using Probot for GitHub to adapting the Sweep self-hosting setup for GitLab. It includes changes to documentation, configuration, and the introduction of a new GitLab app script to facilitate this transition.

Summary

• Adapted the README.md to reflect the transition from GitHub to GitLab, including setup instructions specific to GitLab.
• Updated app.yml to change the app name, URL, and description to be GitLab-specific.
• Introduced a new file gitlab_app.js that implements the GitLab App logic, including OAuth2 authentication and handling GitLab issues.
• The transition aims to leverage GitLab's integrated CI/CD and issue tracking features for a more seamless experience in managing and deploying applications.

Fixes #76.

---

🎉 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]

Rollback Files For Sweep

• Rollback changes to probot/app.yml
• Rollback changes to probot/README.md
• Rollback changes to probot/gitlab_app.js

This is an automated message generated by Sweep AI.

[sweep-ai]

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.