4 posts tagged with "GitHub"

GitHub Actions is a great way to automate builds, tests, deployments, and other CI/CD tasks. But not every job needs to run on every push.

Sometimes you may want to skip a long-running test suite, pause a deployment, avoid unnecessary build minutes, or only deploy when a feature, release, or content update is ready. GitHub Actions already supports conditional jobs with if expressions, but those conditions usually live in your workflow file or depend on repository settings.

That works well for static rules. But when you want to control a workflow dynamically without editing YAML or manually changing GitHub environment variables, feature flags can give a cleaner option.

In this guide, we'll use ConfigCat feature flags in GitHub Actions to decide if the build and deploy jobs should run.

Moving forward with our partnership with @GitHubEducation we have introduced a new plan customized for teachers as part of the GitHub Teachers Toolbox.

ConfigCat Teachers Plan​

You get unlimited ConfigCat Products to make sure there is one for every class, lab and research group each with unlimited Team Members. Also you can add 3 different Permission Groups in every Product to be able to grant proper access rights for everyone.

Show us your most innovative idea in using feature flags with ConfigCat, and we’ll send you a pack of gifts including your choice of video or music streaming worth $100, or books worth $150 + a pack of ConfigCat and GitHub swag + a commercial ConfigCat subscription.

Students should have access to the highest-quality education available. So we partnered with @GitHubEducation and joined the GitHub Student Developer Pack.