Migrating work items to a different project or organization in Azure DevOps isn't as easy it should be. There are various ways to do so, with various levels of complexity and various levels of fidelity (history, for example).
Using GitHub Actions to add a code coverage summary report comment to a pull request and job summary
Publishing Code Coverage and making it look pretty in Azure DevOps is way harder than it should be
A solution to the vague error message that occurs sometimes when deleting/re-creating an agent pool
My personal Azure DevOps pipeline templates
Delete custom fields on a process template in Azure DevOps using the REST API
Using the 'build once deploy many' concepts with an Angular application and Azure Pipelines
Disclaimer I should first off state that I wouldn’t entirely recommend this, if you are migrating to GitHub for the first time, you should try to start off with a blank slate. Keep the old tickets...
Reparent Work Items in the UI If you are reparenting only a few work items, then the easiest way is to use the Mapping view in the Azure DevOps backlog, as described by Microsoft: Enabling the m...
Authenticate to Azure Artifacts from GitHub Actions for builds and code scanning workflows