Github Action

Github Action Rules

• Check if package.json exists in project root and summarize key scripts
• Check if .nvmrc exists in project root
• Check if .env.example exists in project root to identify key env: variables
• Always use git branch -a | cat to verify whether we use main or master branch
• Always use env: variables and secrets attached to jobs instead of global workflows
• Always use npm ci for Node-based dependency setup
• Extract common steps into composite actions in separate files
• Once you're done, as a final step conduct the following:

1. For each public action always use "Run Terminal" to see what is the most up-to-date version (use only major version):

curl -s https://api.github.com/repos/{owner}/{repo}/releases/latest | grep '"tag_name":' | sed -E 's/.*"v([0-9]+).*/\1/'

2. (Ask if needed) Use "Run Terminal" to fetch README.md and see if we're not using any deprecated actions by mistake:

curl -s https://raw.githubusercontent.com/{owner}/{repo}/refs/tags/v{TAG_VERSION}/README.md

3. (Ask if needed) Use "Run Terminal" to fetch repo metadata and see if we're not using any deprecated actions by mistake:

curl -s https://api.github.com/repos/{owner}/{repo} | grep '"archived":'

4. (Ask if needed) In case of linter issues related to action parameters, try to fetch action description directly from GitHub and use the following command:

curl -s https://raw.githubusercontent.com/{owner}/{repo}/refs/heads/{main/master}/action.yml

Converted and distributed by TomeVault — claim your Tome and manage your conversions.