-
Notifications
You must be signed in to change notification settings - Fork 4
[copilot] add comment to parent issue when creating a new issue #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
…references Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
@copilot revert last commit |
…of text references" This reverts commit 108a42a, returning to the simpler REST API approach for issue creation with text-based references instead of GraphQL sub-issue relationships. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Reverted the GraphQL sub-issue implementation as requested. The system now uses the simpler REST API approach with text-based references instead of native GraphQL sub-issue relationships. Changes committed in 2a84325. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
This PR reverts the GraphQL-based sub-issue functionality back to the simpler REST API approach that was in place before.
What Changed
The
create_issue.js
script has been reverted from using GitHub's GraphQL API for creating native sub-issue relationships back to the original REST API implementation that uses text-based references.Current Behavior
When a workflow with
output.issue
configuration is triggered from an issue context, the created output issue will:Example Workflow Behavior
When triggered by issue #123, this workflow will:
Backward Compatibility
All existing workflows continue to work exactly as before. The change only affects the internal implementation of how issue relationships are created, reverting to the proven text-based approach.
Reverts #135.
💡 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.