-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add fields necessary for stale flags #3263
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3263 +/- ##
===========================================
- Coverage 95.95% 76.68% -19.27%
===========================================
Files 1067 1043 -24
Lines 32649 32135 -514
===========================================
- Hits 31327 24644 -6683
- Misses 1322 7491 +6169 ☔ View full report in Codecov by Sentry. |
f0066f2
to
5449bb5
Compare
api/projects/tags/migrations/0005_add_tag_fields_for_stale_flags_logic.py
Show resolved
Hide resolved
The code looks fine, but I felt I needed some questions cleared up for me before approving it. |
5808181
to
7226ced
Compare
Changes
Adds logic necessary to support the stale flags functionality. The relevant changes are:
a.
is_system_tag
- field denoting that the tag is system created, rather than user created (necessary for the tag we plan to add to any flags determined to be stale)b.
is_permanent
- a replacement for the current FE functionality which uses regex to determine if a tag indicates that a feature is 'permanent' and should not be deleted. This is necessary as we will ignore any features tagged with a tag that has this attribute when evaluating if a feature is stale or not.c.
type
- a field to add a new enumerated 'type' field to a tag. This allows us to deterministically find the tag which indicates a feature is stale.Note that there is a related PR in the workflows repository here which adds the relevant tasks, etc. to supplement these changes.
How did you test this code?
Added unit tests.