Merge pull request #824 from cambot/bugfix/checkout-issue-823

Bugfix: checkout issue #823

Author: isc-pbarton

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 - Expanded Baseline Export to include XSL Transforms (#815)
+- Enhanced "Check out branch" to first refresh list of remote branches to eliminate failure due to stale information (#823)
 
 ### Fixed
 - Fix Import All not importing items that do not already exist when compileOnImport is not set (#798)
@@ -18,6 +19,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Fix Revert not syncing files with IRIS (#789)
 - Import All now outputs a warning instead of an error when an item is in the wrong path (#291)
 
+
 ## [2.12.2] - 2025-07-08
 
 ### Fixed

CONTRIBUTING.md

@@ -14,7 +14,7 @@ We encourage use of [Conventional Commits](https://www.conventionalcommits.org/e
 
 Generally speaking, just try to match the conventions you see in the code you are reading. For this project, these include:
 
-* Do not use shortened command and function names. For example, use `set` instead of `s` instead of `set` and `$piece` instead of `$p`
+* Do not use shortened command and function names. For example, use `set` instead of `s` and `$piece` instead of `$p`
 * One command per line
 * Do not use dot syntax
 * Indentation with tabs

cls/SourceControl/Git/Utils.cls

@@ -443,13 +443,14 @@ ClassMethod NewBranch(newBranchName As %String) As %Status
 
 ClassMethod SwitchBranch(targetBranchName As %String) As %Status
 {
-    // Make sure that branch exists first (-a lists both local and remote)
-    do ..RunGitWithArgs(.errStream,.outStream,"branch", "-a")
+    // First, make sure that branch exists
+    do ..RunGitCommand("fetch", .errStream, .outStream, "--prune")    // refresh list of remote branches
+    do ..RunGitWithArgs(.errStream, .outStream, "branch", "-a")       // -a lists both local and remote
     set branches = outStream.Read()
-    if ('$find(branches,targetBranchName)) {
+    if ('$FIND(branches, targetBranchName)) {
         quit $$$ERROR($$$GeneralError, "Selected branch does not exist"_$C(10))
     }
-    k outStream, errStream
+    kill outStream, errStream
     do ..RunGitWithArgs(.errStream, .outStream, "checkout", targetBranchName)
     do ..PrintStreams(errStream, outStream)
     // Checkout can fail due to unstaged changes
@@ -1567,7 +1568,7 @@ ClassMethod ImportRoutines(force As %Boolean = 0, pullEventClass As %String) As
 
     #dim ec as %Status = ..ListItemsInFiles(.itemList, .err)
     quit:'ec ec
-    
+
     // If there is a config file it must be imported before everything else.
     if $Data(itemList(##class(SourceControl.Git.Settings.Document).#INTERNALNAME)) {
         set sc = ##class(SourceControl.Git.Utils).ImportItem(##class(SourceControl.Git.Settings.Document).#INTERNALNAME, force)
@@ -1591,10 +1592,10 @@ ClassMethod ImportRoutines(force As %Boolean = 0, pullEventClass As %String) As
     for  {
         set internalName = $order(itemList(internalName))
         quit:internalName=""
-        
+
         // Don't import the config file a second time
         continue:internalName=##class(SourceControl.Git.Settings.Document).#INTERNALNAME
-        
+
         set context = ##class(SourceControl.Git.PackageManagerContext).ForInternalName(internalName)
         continue:context.Package'=refPackage
         set doImport = ..IsRoutineOutdated(internalName) || force
@@ -2814,7 +2815,7 @@ ClassMethod GetSourceControlInclude(prefix As %String = {%request.URLPrefix}) As
 
 XData ProductionConfigScript [ MimeType = text/javascript ]
 {
-    function checkProductionConfigLoad() {
+function checkProductionConfigLoad() {
         timerState(false);
     }
 

docs/menu-items.md

@@ -1,8 +1,8 @@
 # git-source-control Menu Items
 
-
 ## Status
 This menu option is analogous to the [git status](https://git-scm.com/docs/git-status) command and prints the status of the repository to the output.
+
 ## Settings
 This option opens the GUI's settings page project specific git-source-control settings can be configured. This includes the settings that were configured when running:
 ```
@@ -12,31 +12,49 @@ d ##class(SourceControl.Git.API).Configure()
 This page also includes the mappings configurations.
 
 Any changes made to the settings must be saved using the 'Save' button in order to take effect.
+
 ## Launch Git UI
 This menu option opens the git-source-control GUI. From here commit messages can be written, files can be staged and committed, branches can be viewed.
+
 ## Add
 This menu option is analogous to the [git add](https://git-scm.com/docs/git-add) command. It will perform 'git add' on the currently open file, adding it to the files that can be staged.
+
 ## Remove
 This menu option will only appear if the currently open file has been already added using the 'Add' menu option. It undoes the effect of adding the file, similar to running [git reset](https://git-scm.com/docs/git-reset) on a specific file.
+
 ## Push to remote branch
 This option pushes the commits in the branch to the remote repository. This exhibits the same behavior as the [git push](https://git-scm.com/docs/git-push) command.
+
 ## Push to remote branch (force)
 This option forcibly pushes the commits in the branch to the remote repository. This is potentially destructive and may overwrite the commit history of the remote branch. This exhibits the same behavior as the [git push --force](https://git-scm.com/docs/git-push) command.
+
 ## Fetch from remote
-Much like the [git fetch](https://git-scm.com/docs/git-fetch) command, this option fetches the most recent versions of the branch without merging that version into the local copy of the branch.
+This option first [fetches](https://git-scm.com/docs/git-fetch) the most recent version of the branch without merging that version into the local copy of the branch.  It will then list all files modified between the current version and the remote version.
+
+This also has the effect of refreshing the list of all remote branches and pruning any references that no longer exist in the remote.  (see: [git fetch --prune](https://git-scm.com/docs/git-fetch#Documentation/git-fetch.txt---prune))
+
 ## Pull changes from remote branch
 Much like the [git pull](https://git-scm.com/docs/git-pull) command, this menu option pulls the most recent version of the current branch from a remote source, merging the changes into the local copy.
+
 ## Sync
 This option will synchronize a local repo with the remote repo. The sync operation is only enabled in basic mode. It encapsulates the pattern of fetching, pulling, committing and then pushing into one menu action. If there is no defined remote repository, it will simply commit any uncommitted files.
+
 ## Create new branch
 This menu option creates a new branch in the repository for changes to be committed to. It also changes the current branch to be the created branch. This mimics the behavior of the [git checkout -b](https://git-scm.com/docs/git-checkout) command.
+
 ## Check out an existing branch
-This option changes the currently checkout branch to a chosen branch. This mimics the behavior of the [git checkout](https://git-scm.com/docs/git-checkout) command.
+This option refreshes the local list of branches available in the upstream repository, and then changes the currently checkedout branch to the provided branch.  This mimics the behavior of the [git fetch --prune](https://git-scm.com/docs/git-fetch#Documentation/git-fetch.txt---prune) and [git checkout](https://git-scm.com/docs/git-checkout) commands.
+
+If the desired branch does not exist in your local or in the remote, then you will receive the "Selected branch does not exist" error message.
+
 ## Export all
 This option exports class files to the local file tree at the configured location.
+
 ## Export all (force)
 This option exports all class files regardless of whether they're already up to date in the local file tree or not.
+
 ## Import all
 This option imports the versions of the files that are found in the configured directory into the project. Files that are out of date or the same as the files in the project won't be imported.
+
 ## Import all (force)
-This menu option behaves similarly to the regular import but forces the files to be imported regardless of whether the on-disk version is the same or older. 
+This menu option behaves similarly to the regular import but forces the files to be imported regardless of whether the on-disk version is the same or older.