Apps.Github22
Apps.Github22 copied to clipboard
[FEAT] Send Notification with `Login` ActionBlock When User Not logged In
Why do we need this ?
As a GitHub App developer
I need to:
- Alter/Add Extra information to the Block Notification Send when user runs commands (list mentioned) which needs authentication while not being loggedin.
Command List:
- View your GitHub Profile and Issues -> /github me
- View/Add/Delete/Update Repository Subscriptions -> /github subscribe
- Subscribe to all repository events -> /github Username/RepositoryName subscribe
- Unsubscribe to all repository events -> /github Username/RepositoryName unsubscribe
- Add New Issues to GitHub Repository -> /github issue
- Assign and Share Issues -> /github issues
- So Currently when we run above command for eg for subscribing events we get Notification that
Login to subscribe to repository events ! /github loginbut what we want is and will more helpful: We send Login ActionButton attaching to that same Block while having the MessageYou must be LoggedIn to subscribe repository events. Login to Github.
So That: We will save the key strokes for users to not run command /github login
Glimpses of what should look like:

Acceptance Criteria
- [ ] Alter and Add to same Notify Block with LoginButtons for all commands mention
Further Comments / References
- Also to Note we will have different messages the one that i mention was just for the subscribe event.
- To note we also have ActionsButtons within Modal which needs authentications dont forget to look for same.
Additional comments
- Apart from that we have one know bug (when writing this issue): When we run
/github Username/RepositoryName subscribewithout loggedin we ain't getting any message if we are not loggedIn. which has/ have been fixed #63. which currently provides the simple loginInfo make sure to change it when merging this.
Hey, @samad-yar-khan can you have a look at this, do we need this feat?
Hey @Nabhag8848 Seems like a good thing to have ! thanks for pointing this suggestion
Note:
- Any PRs to this issue will needs to be merge after #63. (Check additional comments above)
Hiya again @Nabhag8848 @samad-yar-khan! Created a PR to fix this issue, kindly review.