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
Add ability to Copy to Clipboard, similar to commit context menu from left panel #6339
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6339 +/- ##
=======================================
Coverage 55.10% 55.11%
=======================================
Files 899 899
Lines 64756 64776 +20
Branches 11627 11629 +2
=======================================
+ Hits 35685 35699 +14
- Misses 26340 26344 +4
- Partials 2731 2733 +2
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seem OK (except for tooltip removal), not tested
I've checked out your revision. There are some visual artifacts:
|
For discussion in #8414 We can get git revision on user request.
Or we can add "GetRevisions" method with commands.
And add revision information on tree build
After
Most likely there is a way to combine both commands. In the current solution, the situation is similar with hidden branches - it shows the last selected one. |
Also for discussion #8414
For fix |
Yes, I think we'll have to do this 👍
If possible I'd rather reduce a number of commands we run (we run a lot of them as is, some commands are run multiple times during the same operation). Pertaining to the discussion in #8414 - if a branch is filtered out of the view, I can't see a good use case where we need to bend over backwards to provide extra information for it. Similar to an inactive remote - there's no information until it is activated and fetched. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand correctly that there is no separation between model and view. Everything is stored in a grid, and after deletion you need to access the repository? |
As I imagine, we have a hash of the commit, and we can get all the necessary information from the model by the hash. (ObjectId) |
Correct, unfortunately there's no separation (and it does bother me). And this makes a lot of thing significantly harder than they should be. E.g. we do a lot of refreshes, which cause flicker, and result in multiple git calls. |
I ran it locally, and something isn't working 100% but I couldn't quite see from the diff. When I right click on the latest master (4355746) in the revision grid and select copy commit:
When I do the same from the left panel I only get the first line:
|
Changed revisions provider.
|
Thank you 🎉 This certainly has been a long journey, thank you for sticking around. |
Fixes #6304
Proposed changes
Screenshots
Before
After
Test methodology
Manually
✒️ I contribute this code under The Developer Certificate of Origin.