Search Results for "CI/CD"

...The system integrates with popular VCS providers and chat tools, surfacing real-time status, logs, and insights so teams can diagnose failures quickly. With autoscaling workers and flexible resource types, Semaphore adapts to small projects and large monorepos alike, turning CI/CD into a reliable, low-friction part of everyday development.

...The app powers the site’s content publishing, episode distribution, and user interactions, including subscriptions and comments. It emphasizes maintainability and transparency, with clear code structure, tests, and CI/CD workflows. Because the repository is open, developers can study its architecture to learn how Phoenix is used in practice for a high-traffic, media-centric website. It also showcases integration with external services for things like audio hosting, search, and analytics, making it an instructive case study for full-stack Elixir development.

...Warning messages have been greatly improved, but are filtered through the legacy formatter to support your existing ignore files. You can optionally use the new Elixir term format for ignore files. You may want to use the --format short argument in your CI pipelines. There are several formats, also there is a new explain feature - for details see CLI options. If you are planning to use Dialyzer with an application built with the Phoenix Framework, check out the Quickstart wiki. Use dialyxir from the directory of the mix project you want to analyze; a PLT file will be created or updated if required and the project will be automatically compiled.

bors-ng is a GitHub merge bot that enforces an “evergreen” main branch by queueing approved pull requests, testing them together on a staging branch, and only advancing main with the exact, passing commit set. Instead of maintainers repeatedly rebasing and merging one PR at a time, bors-ng batches r+-ed PRs, triggers your existing CI (e.g., GitHub Actions), and merges automatically when the batch is green. If a batch fails, it bisects the batch into smaller runs to isolate the culprit, landing the good PRs and kicking only the failing one(s) back for fixes. The bot is implemented as a GitHub App and works alongside—rather than replacing—your CI by reporting commit statuses/checks and acting on PR comments like bors r+ or bors try. ...