no Commits on default merge branch in basic mode

[isc-etamarch]

Fixes #484

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

Attention: Patch coverage is 6.25000% with 15 lines in your changes missing coverage. Please review.

Project coverage is 25.38%. Comparing base (94c92ab) to head (4e642e5).

Files with missing lines	Patch %	Lines
cls/SourceControl/Git/Utils.cls	0.00%	9 Missing ⚠️
cls/SourceControl/Git/Extension.cls	16.66%	5 Missing ⚠️
cls/SourceControl/Git/WebUIDriver.cls	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #536      +/-   ##
==========================================
- Coverage   25.49%   25.38%   -0.12%     
==========================================
  Files          18       18              
  Lines        2608     2624      +16     
==========================================
+ Hits          665      666       +1     
- Misses       1943     1958      +15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[isc-tleavitt]

You can also commit a single modified item from the menu in basic mode - this should also be prevented.

[isc-tleavitt]

One more thought on this: we need to consider usability for a user in basic mode trying to commit/sync. Hiding the "Commit" option and producing different output on the "Sync" option doesn't help our less-technical users. I'd rather see "Commit" enabled (so the user realizes from the menu they have uncommitted changes to the current item) and provide an alert saying they need to create a new branch to commit changes against. Similarly, on Sync, we should be really clear to the user that their work won't be committed - e.g., a big red warning box.

[isc-etamarch]

Added some alerts: