Uh oh!
There was an error while loading. Please reload this page.
Use the new "type" labels after GH migration. - #419
Conversation
Codecov Report
@@ Coverage Diff @@## master #419 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 10 10 Lines 1298 1300 +2 =========================================
+ Hits 1298 1300 +2
|
ezio-melotti
left a comment
There was a problem hiding this comment.
LGTM.
Do you think there's any downside applying it now or is it better/safer to wait? I can still update the labels on my end so that they match the new labels during the migration.
On a more general note, many of the new labels are related to specific dirs/files in the repo, so bevedere will probably need some refactoring so that it can add more labels (also because docs, performance, tests are no longer types).
Uh oh!
There was an error while loading. Please reload this page.
Mariatta
commented
Mar 24, 2022
I would suggest changing the labels first on the CPython repo, and then deploy bedevere afterwards (by merging this PR). |
ezio-melotti
commented
Mar 24, 2022
That makes sense, should we do it now? |
Mariatta
commented
Mar 25, 2022
Yup let's do it! |
ezio-melotti
commented
Mar 25, 2022
Thanks for the PR! |
Closespython/core-workflow#432