| Title | Branching tool does not distinguish between private and public Git mappings |
| Status | open |
| Priority | optional |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | The branching tool has an option "-g" for whether a branch should be registered with Git Fusion. This comes from Git Fusion 1, when all mappings were published. Now we have private and public repos. It should probably always register in the private repos, and the option should control publication. |
| Analysis | 1. Think about policy. 2. Separate private from public Git mapping concepts in the code. 3. Make the option and help text clearer about what it does. |
| How found | unknown |
| Evidence | //info.ravenbrook.com/project/mps/master/tool/branch#13:282-291 |
| Created by | Richard Brooksby |
| Created on | 2016-03-11 14:45:40 |
| Last modified by | Richard Brooksby |
| Last modified on | 2016-03-11 14:45:40 |
| History | 2016-03-11 RB Created. |