-
Couldn't load subscription status.
- Fork 7.3k
issue create: Add special @me assignee (self) #2004
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
issue create: Add special @me assignee (self) #2004
Conversation
|
This differs from the proposed |
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.
|
Once we agree on the flag name I can easily add this same flag to the |
|
@marclop What do you think of supporting a special assignee name GitHub web already supports |
|
@mislav That sounds fine to me, specially if it's how the If so, would we simply treat |
Yes that was my idea. Would you like to change this PR to go into that direction instead? It would just need to cover the assign functionality in |
|
Sorry for the metadata spam! I'm dizzy with issue triage and mistook this for an issue not a PR π€¦ββοΈ |
|
@mislav yep, I'll change the title, description and code when I have the chance. |
|
d452a8c should implement what we discussed |
|
@mislav mind a review when you've got time? Thanks! |
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.
#8 footer
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.
Sorry for the late review! This looks great for the non-web flow of creating issues/PRs β€οΈ
However, it looks to me that the web flow for creating issues/PRs would not resolve @me to the username. The web flow is triggered by either:
- Using the
gh issue/pr create --web flag; - Using the "Continue in browser" option instead of "Submit" in the interactive create flow.
|
@mislav I missed that code path, I'll take a look tomorrow and fix it. |
|
@mislav I've written some tests for the flows:
There remains a problematic case where the user prompts interactive creation of the issue, but specifies assignees: since I have no permissions to triage issues in cli/cli, I'm using my fork Adding metadata to the issue when
|
|
@mislav Hello? Anybody in the house? |
I think this might get addressed in #2472 Thank you for all the work so far, and sorry for the late review! The ball is in our court now; so please bear with us. π |
a7545c1 to
66f5c06
Compare
66f5c06 to
73da25a
Compare
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.
Fantastic, thank you for all your help!
I've pushed updates to make @me available when listing issues as well, so that support for it is consistent across the board. (It was already supported in gh pr list.)
Description
This patch adds a new special handling of the
@mestring when it ispassed as an assignee, to resolve to the currently authenticated user
login which is then resolved to ID using the already existing flow.
Related issues
Closes #965