Skip to content

enhance: Improve shared issue tracker handling in RepositoryConfigure #1610

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

massimopaganigh
Copy link
Contributor

Refactor the handling of shared issue trackers by reusing the Commands.SharedIssueTracker instance. Enhance the removal logic to check for the existence of the tracker file and delete it if empty.

love-linger and others added 5 commits July 21, 2025 17:36
Refactor the handling of shared issue trackers by reusing the `Commands.SharedIssueTracker` instance. Enhance the removal logic to check for the existence of the tracker file and delete it if empty.
@Copilot Copilot AI review requested due to automatic review settings July 21, 2025 11:40
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enhances the shared issue tracker handling in the RepositoryConfigure view model by optimizing object creation and improving cleanup logic. The changes focus on reusing a single SharedIssueTracker instance and adding comprehensive file cleanup when removing issue tracker rules.

  • Refactored to reuse a single SharedIssueTracker instance instead of creating multiple instances
  • Enhanced removal logic to check if the tracker file exists and is empty before deletion
  • Added file system operations to clean up empty issue tracker files

@love-linger
Copy link
Collaborator

Whether to delete the .issuetracker file or keep it as a placeholder file should be decided by the user.

@love-linger love-linger self-assigned this Jul 22, 2025
@love-linger love-linger added the not-planned It's not planned in the future label Jul 22, 2025
@love-linger love-linger force-pushed the develop branch 3 times, most recently from 072502a to 5ce919a Compare July 28, 2025 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-planned It's not planned in the future
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants