Cleanup Codes related to FileDB#5786
Conversation
|
Hi @Okabe-Junya Thanks for the commit 👍 |
|
Thank you - I understand how complex this issue can become, and I will fully respect the team’s opinions. Thanks also for sharing the Slack channel and meeting details; I’ll check them out :) |
|
@khanhtc1202 |
|
Sure, I will explain this on issue 👀 Then we can have check list over there, and discard how we process this issue👌 |
|
Sorry, we updated the CI and branch protection rules. |
|
It appears that CI will not run unless one of the maintainers presses the |
Signed-off-by: Junya Okabe <okabe.junya.qj@alumni.tsukuba.ac.jp>
|
I'm sorry for the reconfirmation, Where else was the code that needs cleaning up in this PR to move forward? |
|
Thanks @Okabe-Junya, I think we can merge this PR to bootstrap the FileDB removal. Other tasks to check will be managed here #5652 (comment) |
Signed-off-by: Junya Okabe <okabe.junya.qj@alumni.tsukuba.ac.jp>
What this PR does:
Remove all FileDB-related code from the codebase
Why we need it:
See #5652
Which issue(s) this PR fixes:
Ref. #5652
(Not
close, since I haven't cleanup-ed docs yet / I haven't decided how to migrate yet)Note:
Per PipeCD’s maintenance and release policy, you’re welcome to target this PR at a different branch or leave it unmerged for a while.
I respect the maintenance team’s policy :)
Does this PR introduce a user-facing change?: