Sweep: allow for rebase.

[sweep-nightly]

Description

This pull request introduces the ability to configure the strategy used for resolving merge conflicts within the SweepAI application. It allows for the use of either the default merge strategy or a rebase strategy, based on an environment variable setting.

Summary

• Added a new environment variable MERGE_CONFLICT_RESOLUTION_STRATEGY in sweepai/config/server.py to configure the merge conflict resolution strategy. The default is set to "merge".
• Modified sweepai/handlers/on_merge_conflict.py to use the MERGE_CONFLICT_RESOLUTION_STRATEGY variable. This change enables the application to choose between a merge or rebase strategy when resolving merge conflicts.
• The merge conflict resolution logic now checks the value of MERGE_CONFLICT_RESOLUTION_STRATEGY and performs either a git merge or git rebase accordingly.

Fixes #3284.

---

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

Rollback Files For Sweep

• Rollback changes to sweepai/config/server.py
• Rollback changes to sweepai/handlers/on_merge_conflict.py

This is an automated message generated by Sweep AI.

[sweep-nightly]

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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sweep-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 8, 2024 5:46pm