Skip to content
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

Merge duplicate issue_template folders in .github for better clarity #1120

Closed
3 of 5 tasks
Brijeshthummar02 opened this issue Oct 31, 2024 · 1 comment · Fixed by #1137
Closed
3 of 5 tasks

Merge duplicate issue_template folders in .github for better clarity #1120

Brijeshthummar02 opened this issue Oct 31, 2024 · 1 comment · Fixed by #1137

Comments

@Brijeshthummar02
Copy link
Contributor

Issue Summary

improve clarity and maintain consistency.

Issue Description

There are currently two issue_template folders in the .github directory, which can cause confusion and may lead to inconsistent issue templates being used. These folders should be merged into a single issue_template folder to improve clarity and maintain consistency.

Proposed Solution (Optional)

Steps to Reproduce:

  1. Navigate to the .github directory in the repository.
  2. Observe the presence of two issue_template folders.

Expected Behavior: There should be only one issue_template folder in the .github directory.

Actual Behavior: Two issue_template folders are present, which may cause redundancy and inconsistency.

Proposed Solution: Merge the contents of both folders into a single issue_template folder, ensuring no template is lost and only one folder remains.

Additional Context: Combining these folders will make it easier for contributors to locate issue templates and will improve the overall organization of the repository.

Note: I have my solution ready. Please assign this issue to me so I can create a PR.

Labels: gssoc, gssoc24, gssoc-ext, good first issue, level1

Priority

Medium - Should be addressed soon

Category

  • Enhancement
  • Refactor
  • Security
  • Design
  • Other

Additional Context (Optional)

No response

Copy link
Contributor

👋 Thank you @Brijeshthummar02 for raising an issue! We appreciate your effort in helping us improve. Our team will review it shortly. Stay tuned!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants