feast-dev/feast-ci-repo-example

Example of how to structure Feast feature repositories & CI for production

Hosted by LF AI & Data Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

feast-dev/feast-ci-repo-example is written in Python and was last pushed on Jul 22, 2021. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 9 minutes ago
Added to GitGenius on October 15th, 2026
Created on July 22nd, 2021
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 5
Total Stargazers: 7 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Feast minimal CI example is a reference implementation that demonstrates how to structure Feast feature repositories and set up continuous integration for production environments.

The project addresses the challenge of managing feature repositories across multiple environments and automating infrastructure updates when feature definitions change. It solves this by providing a concrete example of a CI pipeline that monitors separate staging and production feature repositories, automatically triggering infrastructure updates whenever changes are committed to either directory. This approach allows teams to version control their feature definitions and maintain environment parity while automating the deployment process.

Teams adopting this example should understand that it serves as a template for organizing their own Feast deployments across environments. It suits organizations that need to manage features across staging and production with automated synchronization, particularly those seeking to establish reproducible CI workflows for feature engineering infrastructure. The repository is explicitly positioned as a minimal example, suggesting it provides foundational patterns that teams can extend rather than a complete production-ready system.

The project maintains active engagement with its use case, demonstrating ongoing attention to how Feast feature repositories should be structured in practice. The example-based approach indicates a focus on providing clear, concrete guidance rather than abstract documentation.