The magic command for git to change the URL of the remote repository for the document repo is this:

First get into your local repository.  Using Linux, this would be using the "cd" command. 

Then just to check, say "git remote -v".  It should give you your local name for the remote, typically origin, along with the old url.  Like this:
$ git remote -v
origin https://github.com/AMSAT-NA/pacsat.git (fetch)
origin https://github.com/AMSAT-NA/pacsat.git (push)

Now give the command "git remote set-url origin https://github.com/AMSAT-NA/PacSatDocs.git" and repeat "git remote -v" to check like this:

$ git remote set-url origin https://github.com/AMSAT-NA/PacSatDocs.git
$ git remote -v
origin https://github.com/AMSAT-NA/PacSatDocs.git (fetch)
origin https://github.com/AMSAT-NA/PacSatDocs.git (push)

You can also change the directory name of your local repo to match the remote one if you wish.

======================================
For the code repo, if you are using Code Composer Studio and using the built-in git in CCS, then just right click on the project name in CCS,
and then choose "Team" then "Remote" then "Configure Push To Upstream".  You'll see a line that says

URI: https://github.com/AMSAT-NA/pacsatx.git

Push the change button beside that and change it to "https://github.com/AMSAT-NA/PacSatSW.git"  Hit "save" and you can then do "dry run" if you wish to double check that you types the URL right.

73,

Burns Fisher, WB1FJ
AMSAT(R) Engineering -- Flight Software


On Fri, Mar 3, 2023 at 1:27 PM Burns Fisher (AMSAT) <wb1fj@fisher.cc> wrote:
Hi All,

Bill and I talked this morning and decided (actually confirmed that we both agreed with what we already thought) that the PacSat git repository names are confusing.  Bill and I agreed to change them, and I have done so.

This means that if you have cloned them, you will have to change the upstream names in your local repository to match in order to push upstream.

Here are the changes: 


  1. pacsatx is now PacSatSw  and is to be use only for software (and documentation in the form of comments).
  2. pacsat is now PacSatDocs and is to be used for documentation, including hardware schematics, hardware layouts etc.  
  3. PacSatSw is now WB1FJPacSatToDelete.  This was the original repo that I created 

PacSatSw can be cloned directly into Code Composer Studio--it contains some of the CCS metadata to describe to the compiler where header files are etc.

Currently there are two subdirectories in PacSatDocs:  "requirements" and "reference".  Requirements contains documents about PacSat itself.  Reference contains files taken from other repositories, generally Fox or Golf SVN.  These will usually be PDF files, and are NOT the masters.  If changes are required, they must be made in the source files, which are in their original repositories.

Bill is thinking about what to do regarding hardware, but will probably add a "hardware" folder for schematics etc etc.

WB1FJPacSatToDelete can be deleted if no one is using it.  It has had no checkins since November...it was moved to what is now PacSatSw at that time.

We hope and expect that we will not have to do this again, and we apologize to those who have to change their local git repos.  But hopefully, this renaming makes it a lot more clear what is going on.


73,

Burns and Bill