fix: add migration file to generate stale flags tag for all existing projects #3755
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Currently the stale flags task is failing because it is trying to create stale flags in projects that don't have the tag created in.
This PR adds a migration to add the default tag to all existing projects, note that all new projects already have the tag automatically created.
I also considered the option of having the task create the stale flags tag lazily, but we decided that we want to be able to show our customers that they can get the benefit of stale flags functionality if they upgrade their plan. They are also free to use the tag manually themselves if they want.
How did you test this code?
Ran the migration manually locally to confirm that the tag was created for projects that didn't already have the tag and was not created for those projects that do have it.