-
Notifications
You must be signed in to change notification settings - Fork 204
feat: Implement project enabling/disabling functionality #6363
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: “niladrix719” <[email protected]>
Signed-off-by: “niladrix719” <[email protected]>
Signed-off-by: “niladrix719” <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## master #6363 +/- ##
===========================================
- Coverage 28.82% 17.50% -11.33%
===========================================
Files 560 7 -553
Lines 59941 920 -59021
===========================================
- Hits 17277 161 -17116
+ Misses 41343 738 -40605
+ Partials 1321 21 -1300 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: “niladrix719” <[email protected]>
Signed-off-by: “niladrix719” <[email protected]>
Signed-off-by: “niladrix719” <[email protected]>
|
I think we can still merge this PR, since it will trigger publish_tool.yaml to publish a new version of the codegen image. We can then update the Makefile and gen.yaml image in a later PR. What do you think, @khanhtc1202? Or, we could update the image and use the new one in this PR, but I don’t think I have write access to push a new image version. |
What this PR does:
Why we need it:
Which issue(s) this PR fixes:
Fixes #4754