Skip to content

Can we improve notifications? #2315

Description

@MarcosCobena

Hello,

(I am coming here after closing my initial attempt at #2310.)

After happily using SourceGit in a daily basis for some time, I find a little bit uncomfortable? to dismiss notifications manually. I am used to fetch/pull/push with Ctrl pressed so in some way I expect a more agile workflow (I come from years using Fork, everything told).

In above PR I started with an auto-clear feature, but it is not the idea @love-linger has for the project, so maybe we can find any alternative which fits better.

Thank you in advance!

Activity

  1. love-linger commented on May 7, 2026

    @love-linger
    Collaborator

    I've tested Fork. And in Fork, you also need to close the error dialog manually (at least pressing ESC button)

  2. self-assigned this
    on May 7, 2026
  3. MarcosCobena commented on May 11, 2026

    @MarcosCobena
    Author

    I've tested Fork. And in Fork, you also need to close the error dialog manually (at least pressing ESC button)

    It is true, I have just tested as well. I guess I did not remember Fork showed errors in modal windows, so you are forced to close it before making anything else. If you happen to change tab while an operation is in progress and such fails, the dialog pop ups as well independently on the tab you are right now.

    SourceGit stacks errors in non-modal notifications which actually behave as modal, because you cannot do further operations (fetch again, for instance) before closing them. Having isolated stacks per tab/repository is cool, because they are in context.

    Maybe adding such ESC shortcut can help? I can work on it if you like it. :-)

    Thank you.

  4. MarcosCobena commented on May 11, 2026

    @MarcosCobena
    Author

    I am working on it here: https://github.com/MarcosCobena/sourcegit/tree/feature/clear-notifications-shortcut

    I will use it in a daily basis to see how it behaves.

  5. Repository owner locked and limited conversation to collaborators on May 14, 2026
  6. converted this issue into a discussion #2343 on May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions