Product1 min read

Every flag has an owner now, and stale flags report themselves

A flag without an owner is an outage with a timer on it. Owners are now required, inherited from CODEOWNERS, and stale flags file their own removal tickets.

Priya Raman

Priya Raman

Product Lead, Releases ·

Product cover: Every flag has an owner now, and stale flags report themselves

We looked at 40,000 flags across Driftwire workspaces. The ones that caused incidents had one thing in common more often than any other: nobody knew whose they were.

Owners are required

Every new flag needs an owner: a person or a team. If your repository has a CODEOWNERS file, Driftwire suggests the owner of the code that first reads the flag.

Stale flags report themselves

  • After 30 days at 0% or 100%, a flag is marked stale.
  • Its owner gets one message listing every code reference to remove.
  • With the source control integration on, Driftwire opens the removal pull request itself.

Ownership moves with people

When someone leaves a team in your SSO provider, their flags move to the team. No flag is ever owned by an empty seat.

ProductOwnershipFlag hygiene
Priya Raman

Written by

Priya Raman

Product Lead, Releases

Priya leads product for releases and experiments. Previously ran the deploy pipeline for a payments company where a bad rollout was a bad day for a lot of people.

More posts by Priya Raman