plugins: move transfer-issue to issue management#702
Conversation
✅ Deploy Preview for k8s-prow ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/retest |
|
/cc @petr-muller @stmcginnis, PTAL! |
|
/cc @Prucek |
Signed-off-by: Amulyam24 <amulmek1@in.ibm.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Amulyam24, Prucek The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@Amulyam24 this is good, but do we have an idea about how the transition will look like for instances that enable the Will these blow up with errors on update, or simply lose functionality? I'd like to make sure we do not break instances even if it takes more effort. And if we're not breaking them but they "only" lose functionality until they enable |
Hi @petr-muller, Thanks! This is a good point which I missed, I will try this out and get back. |
|
Hi @petr-muller, I confirmed that with this change, using I can update the announcements page, should it be done post this PR merge? Also, since the page has become kind of obsolete and this change could be breaking, we might have to make the concerned parties explicitly aware, IMO. Atleast Kubernetes and SIGs as a first step, wdyt? |
|
Hi @petr-muller, can you please share your input on the above? |
With the introduction of issue-management, move transfer-plugin to the folder.
Signed-off-by: Amulyam24 amulmek1@in.ibm.com
Assisted-by: AI