// GitHub Projects

A walkthrough of GitHub Copilot Workspace when starting from a GitHub Issue.

GitHub is well-known for version control, and its work with the open source community. But did you know you can use GitHub throughout your development lifecycle? Join Chris Reddington from GitHub's Developer Relations team as he explores how you can use GitHub to plan, code, build, and deploy your work. Learn how the platform comes together in GitHub Issues, Projects, Codespaces, Actions, Copilot and Advanced Security!

In a couple of previous blog posts, I provided a writeup on the GitHub Projects Beta. I wrote two posts on automation within GitHub Projects (Adding Issues to GitHub Projects with GitHub Actions for a user profile and Adding Issues to GitHub Projects with GitHub Actions for an Organization profile). I'm pleased to say that the capabilities went Generally Available last week! As a result of the GA announcement and resulting changes, I need to post updates to my older samples.

A live monthly roundup covering everything notable in Azure, GitHub, and Azure DevOps through February 2022. Key highlights include GitHub Actions support for OpenID Connect (OIDC) deployments to Azure Static Web Apps, GitHub Projects beta improvements (flexible iterations, insights filtering), and updates to GitHub Codespaces and the GitHub CLI. On the Azure side: Azure Monitor gains OpenTelemetry integration and improved observability tooling, Azure Payments HSM enters public preview, and Azure Arc cloud-to-edge observability is explored. Chris also shares Cloud With Chris updates including a new Hugo-powered presentations site hosted on Azure Static Web Apps, a feature flags episode, and community highlights from the UK Azure Community Day.

I recently wrote a blog post about using GitHub Actions to automatically add a GitHub Issue to a GitHub project (Beta) when the issue is opened. I received a question from my colleague and maintainer of the promitor and KEDA Open Source (OSS) Projects, Tom Kerkhove on doing the same with a user-owned GitHub repository, rather than organisation-owned.

In this debut episode of ToolUp Tuesday, Chris and Matt kick off a new series by planning a massively multiplayer management sim game from scratch. They design a microservices architecture, choosing .NET for the world events engine and Go for player decisions, and set up a GitHub repository with GitHub Projects for backlog management.

I've been following the GitHub Projects beta for a while now, and have been fortunate to be accepted as an early adopter. I'm a big fan of the direction, and the flexibility. One of the limitations I've noticed is that there's currently no built-in way to automatically add an issue to a project board. It's on the backlog, but not yet available. Fortunately, GitHub Actions has us sorted. I'll walk you through a sample I put together to do exactly that.

GitHub Issues provides a lightweight project backlog with labels, milestones, assignees, and kanban project boards, while GitHub Discussions (launched at GitHub Universe) enables open community conversations through categorised threads for Q&A, ideas, and show-and-tell. This episode demonstrates converting issues to discussions, automating workflows with GitHub Actions issue and project event triggers, and using project board automation rules.

In this episode, we're going to be taking a slight detour away from GitHub actions and focus on some of the announcements from GitHub universe last week. We're going to explore them both from the announcements, and also take a look at some of those features that have already been released. Stay tuned!