-
Notifications
You must be signed in to change notification settings - Fork 579
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
Add opt-in to always prompt for repo for issue creation and add comment to issue file specifying the repo #6115
Open
mikeseese
wants to merge
3
commits into
microsoft:main
Choose a base branch
from
mikeseese:feat/multi-repo-issue-creation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add opt-in to always prompt for repo for issue creation and add comment to issue file specifying the repo #6115
mikeseese
wants to merge
3
commits into
microsoft:main
from
mikeseese:feat/multi-repo-issue-creation
Conversation
This file contains 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
…hint to new issues Signed-off-by: Mike Seese <[email protected]>
@microsoft-github-policy-service agree |
alexr00
requested changes
Jul 29, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! I have some comments.
… URI scheme Signed-off-by: Mike Seese <[email protected]>
mikeseese
force-pushed
the
feat/multi-repo-issue-creation
branch
from
July 29, 2024 19:27
c9c174f
to
6f68dfc
Compare
@alexr00 It got a little more complex, but now |
LocoabordoR8
approved these changes
Oct 8, 2024
Merge conflict |
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 adds a
githubIssues.alwaysPromptForNewIssueRepo
config variable that defaults tofalse
. When set totrue
, if the user creates a new issue via the+
button in the side panel, the extensions will always prompt the user for a repo to create the issue for instead of using the current open file. Behavior should not change for creating issues from selection/etc that are supposed to be directly contextual.This PR also adds a comment in the
NewIssue.md
file telling the user which repo the issue will be created in if it's available:This PR fixes #2099.