Add "Path To Green" Section to release-schedule.yml

[Copilot]

This PR adds a "Path To Green" section to the issue template used by the release-schedule.yml workflow. This section will help track the release status in dotcom.

Changes:

• Added a new constant pathToGreen for the "Current Path to Green" section
• Added the section to the issue body in both issue creation paths
• Default initial state is green (🟢)

Example of how the section will appear:

## Current Path to Green

Current Status: 🟢

When issues occur, release conductors can update this section to:

## Current Path to Green
Current Status: 🔴

Investigating...

See [Integration Tests PR](https://gh.io/AAkr65h)

Or when green but requiring updates:

## Current Path to Green

Current Status: 🟢 

Path to Green:  #commit-hash1, #commit-hash2

Fixes #6104.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• cdn.fwupd.org
  • Triggering command: /usr/bin/fwupdmgr refresh (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 40f24d1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[francinelucca]

@copilot modify the template so that the path to green section sits on top of the timeline section

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	94.42 KB (0%)
packages/react/dist/browser.umd.js	94.48 KB (0%)

[Copilot]

@copilot modify the template so that the path to green section sits on top of the timeline section

I've moved the "Path to Green" section to sit above the Timeline section in both places where the issue body is constructed. The change was made in commit a9e72ed.

[Copilot]

Pull Request Overview

This PR adds a “Current Path to Green” section to the issue template generated by the release-schedule.yml workflow, allowing release conductors to track release status on dotcom.

• Introduces a pathToGreen constant with the default green status block.
• Inserts the new section into both issue-creation branches of the workflow.
• Ensures an extra blank line follows the section for readability.

Comments suppressed due to low confidence (1)

.github/workflows/release-schedule.yml:120

• The new 'Current Path to Green' section isn't validated by any automated tests. Consider adding or updating unit or e2e tests to assert that generated issues include this section.

const pathToGreen = [

[Copilot]

[nitpick] The repeated manual concatenation of '\n' after each section can be error-prone. Consider using template literals or enhancing the join arrays to include surrounding newlines, reducing extra concatenation calls.

[francinelucca]

Good to go!