Apply GitHub best-practices template updates

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: "GitHub Discussions"
+    url: "https://github.com/RockRunner007/template/discussions"
+    about: "Use discussions for general questions and proposal conversations."
+  - name: "Issue templates"
+    url: "https://github.com/RockRunner007/template/issues/new/choose"
+    about: "Choose a template for bug reports or feature requests."

.github/workflows/test-and-build.yml

@@ -2,9 +2,9 @@ name: Test and Build
 
 on:
   workflow_dispatch:
-#  push:
-#    branches: [ main ]
-#  pull_request:
+  push:
+    branches: [ main ]
+  pull_request:
 
 jobs:
   build-and-test:

.gitignore

@@ -118,6 +118,9 @@ ipython_config.py
 .pdm-build/
 
 # pixi
+
+# VS Code settings and workspace
+.vscode/
 #   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
 #pixi.lock
 #   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one

README.md

@@ -5,6 +5,8 @@
 ![Dependabot](https://img.shields.io/badge/dependabot-enabled-blue.svg)
 ![License](https://img.shields.io/github/license/RockRunner007/template)
 
+> GitHub Community Health: 100% (description, documentation, code of conduct, contributing guidelines, PR template, license, README)
+
 A comprehensive project template for building production-ready services with:
 
 - **Specification-Driven Development** integration with example specs