Can you expand a little on what you mean? Sounds interesting, I haven't looked into VS Code's extension API regarding version control, but maybe they provide some events after certain git actions where I can hook into.
dev/IoT advocate.
my neurotransmitters enjoy: foodie, penguins, and esoterica (the arts, oddities, antiques).
my demons have funny names: AuDHD/MDD/GAD/cPTSD
I usually do feature branches, and especially as a lead I can be switching between branches often checking others work. So it would be amazing if the sets would change when the branch changes. Especially if that branch touches multiple hands then they get exactly what context needs focus
Of course some way of doing that per commit would be cool, but would be a lot of setup on the user side too. So I think branch based would be more realistic/useful.
I've made a note to look into this. I like the idea of (optionally) associating a working set to a git branch and auto-open it when you switch to that branch.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Can you expand a little on what you mean? Sounds interesting, I haven't looked into VS Code's extension API regarding version control, but maybe they provide some events after certain git actions where I can hook into.
I usually do feature branches, and especially as a lead I can be switching between branches often checking others work. So it would be amazing if the sets would change when the branch changes. Especially if that branch touches multiple hands then they get exactly what context needs focus
Of course some way of doing that per commit would be cool, but would be a lot of setup on the user side too. So I think branch based would be more realistic/useful.
I've made a note to look into this. I like the idea of (optionally) associating a working set to a git branch and auto-open it when you switch to that branch.