Generate .devcontainer when creating action

[pelikhan]

---

• ✨ Added Development Container: Introduced devcontainer Dockerfile and configuration for a streamlined development environment (.devcontainer/ directory).

  • Includes Node.js, GitHub CLI, Python3, ffmpeg, and necessary VSCode extensions for GitHub Actions and GenAIScript.
  • Post-create command installs dependencies and adjusts Git configs.

• 📖 Enhanced Descriptions: Updated action.yml and code to dynamically use the script's description or package metadata for descriptions in the action file and README.

• 🛠️ Script Auto-Generation Improvements: Extended action configuration logic for consistent outputs, including better handling of containerized environments (alpine/apt package management).

• ⚙️ Node Version Validation Fix: Improved error messaging for unsupported Node.js versions in VSCode server manager.

• 👩‍💻 New .nvmrc: Added Node.js version management through an lts/* .nvmrc file for consistency.

• 📝 Expanded Output Automation: Refactored .devcontainer settings and ensured they’re written programmatically when generating action files, enhancing environment preparation.

AI-generated content by pr-describe may be incorrect. Use reactions to eval.

[github-actions]

LGTM 🚀

AI-generated content by pr-review may be incorrect. Use reactions to eval.

[github-actions]

Annotations for the Provided Diff

Linter: variable-names

No new functions or variables with improper naming are introduced.

Linter: stats

Here are some basic stats regarding the changes:

Stat	Count
Files Removed	3
Files Added	6
Files Modified	5

Linter: no-fix-mes

No instances of "fixMe" comments were found.

Linter: grumpy-dev

• issue-bot.genai.mts
  Removing the parameters and introducing a dangling getIssue call with env.vars.issue is questionable. What happens if env.vars.issue isn't set? Always check inputs. Back in my day, we didn’t rely on such assumptions, we added validations for every parameter.

• custom-action.yml
  No reason for this ghost file to exist without task blocks. Empty YAML files are not placeholders—they're junk clutter. Delete it or do the job properly.

• docs/src/content/docs/blog/drafts
  Deleting well-written draft blog posts (Debugging Best Practices, State Management, Understanding Prompt Chains)? Why? Saving a few bytes of disk space? Come on. These were helpful. Don’t randomly axe useful content.

• astro.config.mjs
  A 1-line description tweak? Impressive productivity there. Sat idle for how long before realizing this earth-shattering improvement was necessary?

• package.json
  Decrementing Astro dependency? No explanation for rolling back versions? Prepare for bugs if something relied on ^5.8.0. Do the diligence of testing.

Linter: diagrams

Visualizing the overall hierarchy of added/modifications based on the diff:

graph TD
    A[Repo Root] --> |Modified| B[.github/genaisrc/issue-bot.genai.mts]
    A --> |Added| C[.github/workflows/custom-action.yml]
    A --> |Added| D[.github/workflows/genai-issue-labeller.yml]
    A --> |Modified| E[docs/astro.config.mjs]
    A --> |Modified| F[docs/package.json]
    A --> |Removed| G[docs/src/content/docs/blog/drafts/debugging-best-practices.md]
    A --> |Removed| H[docs/src/content/docs/blog/drafts/state-management.md]

Loading

Linter: description

The pull request description does not adequately detail changes in the diff. It fails to mention:

1. Removed blog drafts on debugging, state management, and prompt chains.
2. Additions of multiple empty YAML files within .github/workflows.

Improve the description to include all impactful changes, especially content deletions and workflow tweaks.

Linter: comments

Files like issue-bot.genai.mts lack sufficient comments clarifying purpose or new logic. Example: Why was parameters removed? What safeguards ensure env.vars.issue always exists? Add comments to explain key decisions or edge cases handled.

AI-generated content by linters may be incorrect. Use reactions to eval.