David Puplava

@dotnet-policy-service agree

> IMHO we either revert the task rename or create a migration to avoid breaking existing workflows That's the right thing to do. I'll try and add a database migration...

> please create a database migration and let me know if you need help on this @hishamco I added a Data Migration but it doesn't seem to run even though...

> Please update the PR to show why the migration is not working False alarm. I have the migrations working now. I overlooked that migration was already applied while testing....

> @davidpuplava for instructions on how to resolve the merge conflicts due to https://github.com/OrchardCMS/OrchardCore/issues/16572 please follow the step listed in https://github.com/OrchardCMS/OrchardCore/issues/16572#issuecomment-2291836365. Thanks @MikeAlhayek, your comment instructions worked well. One additional...

I've tested against the X/Twitter v1.1 API and confirm the `UpdateXTwitterStatusTask` works as expected. I've re-requested reviews as mentioned I should do earlier. But...I'm not certain that changing the workflow...

> Zoltan I think we did similar things in both Azure AD & Facebook Meta Yes, looks like UI strings were updated to use the Meta and EntraID names, but...

This PR is ready for review. I changed type/class/id names back to their original names prior to the rebrand based on what I could find in #15528 but I left...

That is the other post I used as well! Thanks for finding it (I couldn't for the life of me find it when I opened the issue.) I don't know...