Standardized GitHub Workflows

This repository provides production-ready, secure, and standardized GitHub Actions workflows for multi-stack development teams (Flutter, Go, Python, and Bash).

🚀 Quick Start

To use the standardized release workflow in your own repository:

1. Create a .github/workflows directory in the root of your project if it doesn't already exist.
2. Copy the release.yml file from this repository into your .github/workflows/ folder.
3. Customize the Build Artifacts step inside the YAML file based on your project's technology stack (Go, Flutter, or Python).
4. Push a semantic version tag to trigger the release:

git tag v1.0.0
git push origin v1.0.0

Supported Stacks & Build Rules

1. Go

Automatically builds binary files and attaches them to the GitHub Release.

2. Python

Builds source distributions and wheels using modern Python packaging standards.

3. Flutter

Handles dependency resolution and builds release artifacts (APKs, bundles, or desktop binaries).

🔒 Security Best Practices

Uses strict permission scopes (contents: write).

Pins GitHub Action versions to secure commits/tags.

.github/
│
├── workflows/                # Production-ready GitHub Actions workflows
│   ├── ci-node.yml           # CI standard pipeline for Node.js projects
│   ├── ci-flutter.yml        # CI standard pipeline for Flutter projects
│   ├── release-semantic.yml  # Automated semantic versioning release workflow
│   └── security-scan.yml     # Security and vulnerability scanning checks
│
├── templates/                # Standardized contribution and issue templates
│   ├── pull_request_template.md
│   └── issue_template/
│
├── linters/                  # Shared linter and formatter configurations (ESLint, Prettier, EditorConfig)
└── docs/                     # Documentation, guides, and developer resources