5 Repos
Mechanisms that initiate automated build or restart tasks upon detecting file system changes.
Distinct from Directory Change Trackers: Distinct from Directory Change Trackers: focuses on triggering build actions rather than just reporting directory state changes.
Explore 5 awesome GitHub repositories matching development tools & productivity · Build Triggers. Refine with filters or upvote what's useful.
Air is a command-line utility designed to automate the development lifecycle for Go applications. It functions as a build runner that monitors source code for file-system modifications, automatically triggering rebuilds and process restarts to maintain an updated development environment. The tool distinguishes itself by integrating container-isolated execution, allowing developers to run build and test workflows within consistent, ephemeral environments. It also incorporates a reverse-proxy layer that intercepts network traffic to facilitate live-reloading of browser sessions, ensuring that c
Triggers application rebuilds and restarts automatically when source code files are modified.
Watchman is a filesystem change monitor and recursive directory watcher that operates as a background service to track file modifications in real time. It functions as an event-driven file trigger and state query engine, allowing users to retrieve directory snapshots and lists of changed files since a previous check. The project provides tooling for incremental builds by identifying exactly which files have changed to compile only necessary project components. It is designed for large scale directory watching, monitoring massive file trees while executing external commands or scripts automati
Initiates automated build or restart tasks immediately after source code files are modified.
Flux is a Kubernetes GitOps delivery tool used to automate application deployments by synchronizing cluster state with configurations stored in Git, OCI, or Helm repositories. It functions as a set of controllers that monitor desired state in external sources and continuously reconcile the live cluster to match those definitions. The system distinguishes itself through a multi-cluster management plane that coordinates application delivery across fleets of remote clusters from a central hub. It provides a dedicated mechanism for automated image updates, which scans container registries for new
Subscribes to repository events and triggers custom logic when revisions change.
This is a GitHub Action that automates FTP and FTPS file transfers, enabling continuous deployment directly from a repository. Triggered by code pushes or other repository events, it reads server credentials exclusively from encrypted GitHub Secrets to keep access credentials secure. The action supports both deploying files and previewing what changes would occur before applying them. Built for reliable synchronization, the action computes a minimal set of upload and deletion operations by comparing the local file tree against the remote directory structure. It transfers files sequentially ov
Triggers on repository events such as code pushes, receiving all configuration through environment variables.
This project serves as a comprehensive technical guide and framework for building, deploying, and managing event-driven applications. It focuses on serverless architecture development, providing patterns and practices for implementing cloud-native services that execute code in response to triggers without requiring persistent server infrastructure. The repository distinguishes itself by offering a unified approach to polyglot runtime orchestration, allowing developers to manage components written in multiple programming languages within a single project. It emphasizes local cloud emulation, e
Provides controllers that subscribe to version control events to execute custom logic upon repository activity.