Skip to content
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

Support options in git_status.fetch() #2287

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

kanielrkirby
Copy link

@kanielrkirby kanielrkirby commented Jul 6, 2024

It looks like support was available/built-in, but possibly left out for some reason?

Happy to rework, this is just to start conversations :)

This Pull Request fixes/closes #2263.

I followed the checklist:

  • I added unittests
  • I ran make check without errors
  • I tested the overall application
  • I added an appropriate item to the changelog

It would also be good to know your stance on the ? idea, or any other additions you might want to this to make this mergeable.

It looks like support was available/built-in, but possibly left out for some reason?

Happy to rework, this is just to start conversations :)
@kanielrkirby
Copy link
Author

I just realized I got it backwards! That is totally my bad 😅

@extrawurst
Copy link
Owner

thanks for looking into this. i wonder what blame tells us how this got overseen - I assume no one ever used it so it went unnoticed 🙈

@extrawurst extrawurst added this to the v0.27 milestone Jul 6, 2024
@kanielrkirby
Copy link
Author

kanielrkirby commented Jul 6, 2024

thanks for looking into this. i wonder what blame tells us how this got overseen - I assume no one ever used it so it went unnoticed 🙈

It seems to be, it's been 3 years! To be completely fair, most people (myself included) don't know how Git works in most cases. All you usually need is the good ol' clone <repo>; add <things>; commit -m <changes>; push;

I remember seeing this was from Stephan Dilly (though I'm not sure who that is, he's in a lot of the old code. Is that your old handle / name perhaps? Or an old maintainer?)

After blaming (using the recursive blame I just added! haHA!!), the project at that point was (as far as I can tell) fully able to support it (the options were there already). Maybe it was just planned to be done in a separate commit.

@ondrej-ivanko
Copy link

I'm glad someone is working on this. Thank you guys. I use stashing a lot, so this would definitely help me.

I suppose this solution doesn't really change anything in the functionality, when user swaps different values in Options -> Status -> Show untracked on Stash tab [4]. In my case switching to different values in the Show untracked option doesn't change what files are displayed on Stash tab [4], only what files are displayed on Status tab [1].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stashing tab shows not staged/ not tracked files in view
3 participants