[copilot] add comment to parent issue when creating a new issue#136
Merged
[copilot] add comment to parent issue when creating a new issue#136
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] [copilot] output issue in an issue context
Add subissue functionality to create_issue.js script for issue context workflows
Aug 20, 2025
pelikhan
reviewed
Aug 20, 2025
…references Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
|
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
AI
changed the title
Add subissue functionality to create_issue.js script for issue context workflows
Implement GraphQL-based sub-issue relationships for create_issue.js script
Aug 20, 2025
Collaborator
|
@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>
Contributor
Author
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:
|
Copilot
AI
changed the title
Implement GraphQL-based sub-issue relationships for create_issue.js script
Revert GraphQL sub-issue implementation back to REST API approach
Aug 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.jsscript 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.issueconfiguration 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.