add github templates and update namespace and group of this project

[NeatGuyCoding]

Summary by CodeRabbit

• Chores
  • Added standardized GitHub issue templates for bug reports and feature requests
  • Added issue template configuration to guide issue submission workflows
  • Added pull request template for consistent PR descriptions
  • Updated contribution guidelines with streamlined structure and modern testing practices
  • Updated project metadata URLs and README to reflect active maintenance and new organization

[coderabbitai]

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Adds standardized GitHub issue and pull request templates with configuration, reorganizes contribution guidelines for clarity, updates README to reflect active maintenance, and migrates project metadata to the new GitHub organization (socketio4j).

Changes

Cohort / File(s)	Summary
GitHub Issue Templates .github/ISSUE_TEMPLATE/bug_report.md, feature_request.md	New structured issue templates with YAML front-matter (name, about, title, labels, assignees) and organized sections for bug reports and feature requests to standardize issue submissions.
GitHub Templates Configuration .github/ISSUE_TEMPLATE/config.yml, .github/pull_request_template.md	New configuration disabling blank issues and redirecting questions to discussions; new PR template with standardized sections (Description, Type of Change, Checklist, Testing) to guide PR authors and reviewers.
Contribution Documentation CONTRIBUTING.md	Reorganized sections (Project Structure → Development Environment → Quick Start); modernized guidance (JUnit 4 → JUnit 5), simplified fork/clone workflow to upstream/main; consolidated PR, code style, and testing sections; removed legacy DCO and Release Process details.
Project Metadata README.md, pom.xml	Updated README to reflect active fork maintenance; migrated GitHub organization URLs from NeatGuyCoding to socketio4j in pom.xml (project <url>, <scm>/<url>, <scm>/<connection>).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

• CONTRIBUTING.md: Substantive reorganization and content refactoring—verify section reordering improves clarity and no guidance is lost or contradicted across sections.
• pom.xml: URL migrations—confirm all three metadata references are correctly updated and match the new organization structure.
• README.md: Semantic shift in project status—ensure messaging is consistent with organizational changes elsewhere in the PR.

Poem

🐰 With templates and forms now neatly arranged,
The socketio4j home has been rearranged,
From questions to PRs, a smoother new way,
Contributing guidance brightens the day,
The fork springs to life, maintained and at play! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: adding GitHub issue/PR templates and updating project namespace/organization references from NeatGuyCoding to socketio4j across multiple files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature-new-documentation-template-neatguy-1117

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull Request Overview

This PR updates the project's GitHub organization namespace from NeatGuyCoding to socketio4j and adds standardized GitHub templates for issues and pull requests.

• Updated repository URLs in pom.xml, README.md, and CONTRIBUTING.md to reflect the new socketio4j organization
• Simplified and streamlined the CONTRIBUTING.md documentation
• Added GitHub issue templates for bug reports and feature requests, along with a PR template

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
pom.xml	Updated SCM URLs from NeatGuyCoding to socketio4j organization
README.md	Updated project description and removed outdated branching information
CONTRIBUTING.md	Streamlined contribution guidelines, updated upstream remote URL to socketio4j, and simplified documentation structure
.github/pull_request_template.md	Added standardized PR template with checklist and structured sections
.github/ISSUE_TEMPLATE/feature_request.md	Added feature request template with consistent formatting
.github/ISSUE_TEMPLATE/config.yml	Added issue template configuration linking to discussions
.github/ISSUE_TEMPLATE/bug_report.md	Added bug report template with environment details and structured sections

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull Request Overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/pull_request_template.md (1)

7-7: Minor wording suggestion for Type of Change options.

The phrasing "Bug fix (non-breaking change which fixes an issue)" could be slightly improved for formality. Consider: "Bug fix (non-breaking change that resolves an issue)" or "Bug fix (non-breaking change to resolve an issue)" for more formal wording.

Also applies to: 7-7

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ce825ba and 0aec551.

📒 Files selected for processing (7)

• .github/ISSUE_TEMPLATE/bug_report.md (1 hunks)
• .github/ISSUE_TEMPLATE/config.yml (1 hunks)
• .github/ISSUE_TEMPLATE/feature_request.md (1 hunks)
• .github/pull_request_template.md (1 hunks)
• CONTRIBUTING.md (5 hunks)
• README.md (1 hunks)
• pom.xml (1 hunks)

🧰 Additional context used

🪛 LanguageTool

.github/pull_request_template.md

[style] ~7-~7: Consider using a different verb for a more formal wording.
Context: ... [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaki...

(FIX_RESOLVE)

🔇 Additional comments (9)

README.md (2)

3-3: Active fork narrative is clear and informative.

The update effectively communicates the project's active maintenance status, replacing the previous "no longer actively maintained" statement. This aligns well with the project reorganization under the socketio4j organization.

Also applies to: 3-3

---

13-39: Migration section is well-structured with clear dependency replacement examples.

The before/after Maven dependency examples make it straightforward for users upgrading from the original netty-socketio. The note about Spring integration using SpringAnnotationScanner is helpful context.

pom.xml (1)

11-11: Project URLs consistently updated to socketio4j organization.

All three URL references (project URL and SCM URLs) correctly point to the new organization namespace. This ensures proper attribution and links in Maven Central and related tools.

Also applies to: 11-11

.github/pull_request_template.md (1)

1-44: PR template provides clear structure and helpful guidance.

The template appropriately aligns with the contribution guidelines defined in CONTRIBUTING.md, including type categories, testing requirements, and commit message conventions. The checklist effectively encourages contributors to verify quality standards before submission.

CONTRIBUTING.md (2)

87-87: Previous review feedback on JUnit documentation has been properly addressed.

The Testing section now correctly documents that "JUnit 5 for new tests. JUnit 4 is also supported for legacy tests (both are available via Maven dependencies)." This accurately reflects the dual JUnit support evident in pom.xml.

Also applies to: 87-87

---

26-42: Quick Start section properly references socketio4j organization.

The git commands correctly point to the new organization namespace for both the fork clone and the upstream remote. This aligns with the project rebranding in this PR.

.github/ISSUE_TEMPLATE/config.yml (1)

1-6: Issue template configuration enforces structured submissions appropriately.

Disabling blank issues and providing a discussion link ensures that substantive questions go to Discussions while structured bug reports and feature requests use the provided templates. The socketio4j organization URL is correctly referenced.

.github/ISSUE_TEMPLATE/bug_report.md (1)

1-48: Bug report template provides comprehensive structure for issue submission.

The template effectively guides users to provide essential debugging information: reproduction steps, environment details, code examples, and stack traces. The module selector appropriately constrains to the integration modules where framework-specific issues typically arise. Title prefix and label assignment will help with organization and filtering.

.github/ISSUE_TEMPLATE/feature_request.md (1)

1-33: Feature request template encourages thorough problem analysis and design consideration.

The progression from motivation (use case) through design (proposed solution and alternatives) to impact assessment (module, breaking changes, compatibility) creates a thoughtful submission process. This helps distinguish from premature requests and surfaces important considerations early.