Duplicate Issues Improvements

[mor39a]

Context of Contribution

• Bug Fix
• Refactoring
• New Feature
• Others

Summary of the Proposal

• Added a config.yml file to include a message that reiterates the request to check for duplicates before creating a new issue.
• Added a GitHub Action that identifies potential duplicate issues and pull requests covering the same topic.

Reason for the new feature

Given the number of duplicate issues that have been created, I've implemented a set of features aimed at discouraging their creation and improving duplicate issue detection

Checklist

• I have read the CONTRIBUTING.md and agree to follow it.
• This PR does not contain commits of multiple contexts.
• Code follows proper indentation and naming conventions.
• Implemented using only APIs that can be submitted to the Microsoft Store.
• Works correctly in both dark theme and light theme.
• Works correctly on any device.

[mor39a]

This feature was implemented using AI assistance and is pending verification to ensure it works as expected

[Kyome22]

@mor39a Rather than putting scripts directly into the YAML file, I prefer creating a .github/scripts/ directory, placing the executable scripts there, and then calling them from the workflow.

[Kyome22]

Basically, GitHub Actions can't even be run until they are merged. So, I think we should merge it once it looks good enough and then create follow-up PRs to make adjustments as needed.

[mor39a]

@mor39a Rather than putting scripts directly into the YAML file, I prefer creating a .github/scripts/ directory, placing the executable scripts there, and then calling them from the workflow.

Ok, I'll separate them then.

Basically, GitHub Actions can't even be run until they are merged. So, I think we should merge it once it looks good enough and then create follow-up PRs to make adjustments as needed.

I don't recommend implementing features without testing them first. I was planning to run them in a test repository.

[mor39a]

We could also set it up to add a “potential-duplicate” label. What do you think, @Kyome22?

await github.rest.issues.addLabels({
  owner: owner,
  repo: repo,
  issue_number: issue.number,
  labels: ['potential-duplicate']
});

[Kyome22]

I don't recommend implementing features without testing them first. I was planning to run them in a test repository.

Of course, if it's possible to set up a test repository and experiment there, that would be even better.

[Kyome22]

We could also set it up to add a “potential-duplicate” label. What do you think, @Kyome22?

await github.rest.issues.addLabels({
  owner: owner,
  repo: repo,
  issue_number: issue.number,
  labels: ['potential-duplicate']
});

Adding labels sounds like a great idea. I'm on board with that.