This repository contains a comprehensive collection of reusable GitHub Actions workflows for iExec projects. These carefully crafted workflows can be seamlessly integrated into your projects to standardize and automate common CI/CD tasks, saving you time and ensuring consistency across your development pipeline.
Automates the process of building, tagging, and pushing Docker images to Docker Hub. Perfect for projects that require containerization with minimal configuration overhead.
Uses the release-please-action to automate versioning and changelog generation based on Conventional Commits. This workflow streamlines your release process and ensures consistent version management.
Automates the process of publishing NPM packages to the NPM registry with highly configurable options. Simplifies the package publishing workflow while maintaining security and reliability.
Validates that pull request titles follow the Conventional Commits specification for better repository management. Ensures your commit history remains clean and meaningful for improved collaboration.
Provides a standardized workflow for building, testing, and publishing Rust packages with intelligent caching and comprehensive artifact management. Optimized for Rust projects of all sizes.
Automatically identifies and closes stale issues and pull requests to maintain a clean and focused repository. Helps your team concentrate on active work items and reduces maintenance overhead.
Each workflow has its own detailed documentation in its respective directory. The comprehensive documentation includes:
- 📄 Detailed overview of the workflow's purpose and functionality
- 🔒 Required inputs, secrets, and environment variables
- ⚙️ Extensive configuration options with examples
- 💻 Complete example usage with annotations
- 🔍 Troubleshooting tips and best practices
- 🔄 Standardization: Ensure consistent CI/CD processes across all your projects with battle-tested workflows
- 🛠️ Maintainability: Centralized workflows make updates and improvements easier to manage, reducing technical debt
- 📋 Reduced Duplication: Avoid copying and pasting workflow configurations between repositories, eliminating drift and inconsistencies
- ✅ Best Practices: Implement industry best practices for building, testing, and deploying applications with minimal effort
- ⏱️ Time Savings: Reduce the time spent configuring and maintaining CI/CD pipelines across multiple projects
- 🔍 Visibility: Improve transparency and observability of your development processes
- 🚀 Scalability: Easily scale your CI/CD practices as your organization grows