Responds with a nice error page for Radix (and Equinor) based on the requested domain
Commits to the main branch must follow Conventional Commits and uses Release Please to create new versions.
Radix Ingress Default Backend follows the Conventional Commits and uses Release Please to create new versions.
All commits to main should either start with feat: or with fix: (a ! will suggest a major version bump).
Release-Please will create a PR with for a new Release with all unreleased commits, bumping the version according to the commit message, linking the PRs and writing a nice CHANGELOG.
After a new version is released, we need to update radix-flux to start using it.
Each commit to main will also build a nightly build that can be used if required.
Radix Ingress Default Backend makes use of GitHub Actions for build checking in every pull request to the main branch. Refer to the configuration file of the workflow for more details.
Read our contributing guidelines