feat: extend user patterns for autocmd

[timeitel]

Hi, thanks for this plugin. Can the events be extended to also include the ones from Neogit?
It would also be helpful to expose a refresh function if possible for user maps.

[mikesmithgh]

Hey @timeitel thanks for the PR

It would also be helpful to expose a refresh function if possible for user maps.

You can refresh like this 🙂

require('git-prompt-string-lualine').set_prompt_and_refresh()

Can the events be extended to also include the ones from Neogit?

I am not opposed to adding them. I am just curious if they are actually needed. git-prompt-string-lualine has a filewatch https://github.com/mikesmithgh/git-prompt-string-lualine.nvim/blob/main/lua/git-prompt-string-lualine/autocmd.lua#L35 and I would expect that to trigger a refresh on any git pull/push/commit regardless of how it occurred. Are you not seeing updates when you do a Neogit operation?

[timeitel]

Hey @timeitel thanks for the PR

It would also be helpful to expose a refresh function if possible for user maps.

You can refresh like this 🙂

require('git-prompt-string-lualine').set_prompt_and_refresh()

Can the events be extended to also include the ones from Neogit?

I am not opposed to adding them. I am just curious if they are actually needed. git-prompt-string-lualine has a filewatch https://github.com/mikesmithgh/git-prompt-string-lualine.nvim/blob/main/lua/git-prompt-string-lualine/autocmd.lua#L35 and I would expect that to trigger a refresh on any git pull/push/commit regardless of how it occurred. Are you not seeing updates when you do a Neogit operation?

Thanks for mentioning the refresh and adding more events!
From testing I just realised the git operations aren't triggering any refresh when the working directory is a git worktree.
Possibly because FileChangedShellPost won't be triggered from commits since the .git folder is outside the CWD?

[mikesmithgh]

Thanks for mentioning the refresh and adding more events! From testing I just realised the git operations aren't triggering any refresh when the working directory is a git worktree. Possibly because FileChangedShellPost won't be triggered from commits since the .git folder is outside the CWD?

Could you provide an example of the directory structure or steps to reproduce?

[timeitel]

Thanks for mentioning the refresh and adding more events! From testing I just realised the git operations aren't triggering any refresh when the working directory is a git worktree. Possibly because FileChangedShellPost won't be triggered from commits since the .git folder is outside the CWD?

Could you provide an example of the directory structure or steps to reproduce?

I realised it's not working for bare repos, just fyi

[mikesmithgh]

Thanks for mentioning the refresh and adding more events! From testing I just realised the git operations aren't triggering any refresh when the working directory is a git worktree. Possibly because FileChangedShellPost won't be triggered from commits since the .git folder is outside the CWD?

Could you provide an example of the directory structure or steps to reproduce?

I realised it's not working for bare repos, just fyi

@timeitel Thanks for the info. Yep, git-prompt-string should just detect a bare repo but can't perform the same as if it was in a working tree. The branch would just look something like BARE:main. Is that the issue you were seeing, or is there some other workflow you have? (I may be missing something if you have a different workflow than me)

[timeitel]

Thanks for mentioning the refresh and adding more events! From testing I just realised the git operations aren't triggering any refresh when the working directory is a git worktree. Possibly because FileChangedShellPost won't be triggered from commits since the .git folder is outside the CWD?

Could you provide an example of the directory structure or steps to reproduce?

I realised it's not working for bare repos, just fyi

@timeitel Thanks for the info. Yep, git-prompt-string should just detect a bare repo but can't perform the same as if it was in a working tree. The branch would just look something like BARE:main. Is that the issue you were seeing, or is there some other workflow you have? (I may be missing something if you have a different workflow than me)

Sorry I should say, the issue is specifically when using a git worktree. For example, create a worktree, make any git change like commit or push with the neovim terminal, and there's no update in git-prompt-string until refocusing the application.