Justine Tunney

@michaeldfallen No I would propose the `.git-radar.bashrc` replace the existing `PS1` entirely. If someone installs your script, they've given you permission to replace their bash prompt. If they want their...

@marcvangend Then they would just say in their `.bashrc`: ``` bash source ~/.git-radar.bashrc PS1="rofl bzr $PS1" ```

@zx8 Wow thanks for finding that bug. I updated the code in my original comment. PTAL? I'm not 100% sure what the best approach is, since I don't know everything...

@zx8 The ## syntax wouldn't work since the `HEAD` file contains `ref: refs/heads/branch` on my end. I guess I could just say `${h##ref: refs/heads/}` though. But that would be more...

Our team probably can't do something like this at the moment. I suspect configuring color might be more appropriate if done in code/config rather than UI.

Is the root problem that colors are not predictable and might change as you add additional runs? I'm not sure how color selection works at the moment. Although one possible...

We're currently building SQL support so Runs can be grouped into Experiments, Experiments can be grouped into Projects, which are owned by Users. The next logical step is to add...

One thing you might be able to do is render a matplotlib image and log it as an image summary.

What do we think about the following solutions? 1. Have a checkbox next to regex search so it chooses new colors each time it's applied. 2. Make (1) the default...

Right now it's a placeholder for some code we might modularize outside the TensorFlow codebase. Tell me more about what you want it to be? [See also](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/tensorboard/db).