Github Code References

Github Code References is an integration that enables you to discover feature flag and configuration references within your codebase. By leveraging the Github API, it provides visibility into where these references are used without storing sensitive information.

This integration is crucial for streamlining feature management and maintaining organized code. It allows you to easily identify which parts of your codebase are impacted by specific feature flags or configurations. With Github Code References, you can:

  • Quickly locate feature flag and config usage across your repositories

  • Understand the scope and impact of each feature flag or config

  • Maintain a clean and organized codebase by identifying unused or stale references

By integrating Github Code References into your development workflow, you can ensure that your feature flags and configurations are properly managed. This helps prevent technical debt and makes it easier to reason about your codebase as it evolves over time.

Key benefits of Github Code References include:

  • Improved code organization and maintainability

  • Faster troubleshooting and debugging of feature flag issues

  • Easier collaboration among team members working on the same codebase

  • Reduced risk of deploying unintended changes or outdated feature flags

Ultimately, Github Code References provides a powerful tool for teams looking to optimize their feature management practices. By leveraging the Github API and providing clear visibility into flag and config usage, it helps ensure a more efficient and effective development process.

Configuration and setup process

To get started with the Github Code References integration, you'll need to create a Github developer token. This token should have read access to the organization or repositories where you use Statsig. You can find this option in Github under Settings > Developer Settings > Personal Access Token.

Once you have your token, log in to the Statsig Console and navigate to the Github Code References integration on the Integrations page. This can be found in Project Settings > Integrations Tab > Github Code References. The integration will provide additional instructions on how to enable it.

Input your Github token and organization name into the integration. It will then verify that it can access your repositories and notify you if there are any issues. After successful verification, you're ready to view your code references!

To access your code references, navigate to the Feature Gates or Dynamic Configs pages on the Statsig Console. Select a specific gate or config, then click on the Diagnostics tab. Here, you'll find a "View Code References" link that will display all the places in your code where that gate or config is referenced.

You can filter the code references by repository and file extension, making it easy to find exactly what you're looking for. This integration helps you quickly identify where your feature gates and dynamic configs are being used across your codebase.

The Github Code References integration is a powerful tool for understanding how your feature flags and dynamic configurations are being utilized. By setting it up, you gain valuable insights into your codebase and can make more informed decisions about your Statsig implementation.

Advanced features and best practices

The Github Code References Action automates scanning and PR creation for stale gates. This powerful feature streamlines the process of updating your codebase.

You can easily filter code references by repository and file extension on the Statsig Console. This allows you to quickly find the relevant code references for your feature gates and dynamic configs.

When moving from POC to production with Github Code References, follow best practices:

  • Ensure your Github token has appropriate permissions

  • Configure the action to run on a regular schedule

  • Review and merge PRs in a timely manner

Take advantage of additional resources to get the most out of Github Code References:

  • Statsig documentation provides in-depth guides and examples

  • The Github Marketplace listing includes usage instructions and configuration details

  • Join our community support channels to ask questions and share tips with other users

By leveraging the advanced features of Github Code References and following best practices, you can efficiently manage your feature gates and dynamic configs directly from your codebase. The automated scanning and PR creation saves valuable engineering time, while the filtering capabilities provide quick access to the references you need.

As you move from POC to production, lean on the wealth of resources available—from comprehensive documentation to helpful community support. With Github Code References, you have a powerful tool to streamline your feature management workflow and keep your codebase up-to-date.

Join the #1 experimentation community

Connect with like-minded product leaders, data scientists, and engineers to share the latest in product experimentation.

Try Statsig Today

Get started for free. Add your whole team!

Why the best build with us

OpenAI OpenAI
Brex Brex
Notion Notion
SoundCloud SoundCloud
Ancestry Ancestry
At OpenAI, we want to iterate as fast as possible. Statsig enables us to grow, scale, and learn efficiently. Integrating experimentation with product analytics and feature flagging has been crucial for quickly understanding and addressing our users' top priorities.
OpenAI
Dave Cummings
Engineering Manager, ChatGPT
Brex's mission is to help businesses move fast. Statsig is now helping our engineers move fast. It has been a game changer to automate the manual lift typical to running experiments and has helped product teams ship the right features to their users quickly.
Brex
Karandeep Anand
President
At Notion, we're continuously learning what our users value and want every team to run experiments to learn more. It’s also critical to maintain speed as a habit. Statsig's experimentation platform enables both this speed and learning for us.
Notion
Mengying Li
Data Science Manager
We evaluated Optimizely, LaunchDarkly, Split, and Eppo, but ultimately selected Statsig due to its comprehensive end-to-end integration. We wanted a complete solution rather than a partial one, including everything from the stats engine to data ingestion.
SoundCloud
Don Browning
SVP, Data & Platform Engineering
We only had so many analysts. Statsig provided the necessary tools to remove the bottleneck. I know that we are able to impact our key business metrics in a positive way with Statsig. We are definitely heading in the right direction with Statsig.
Ancestry
Partha Sarathi
Director of Engineering
We use cookies to ensure you get the best experience on our website.
Privacy Policy