Steve Kieffer

> the PR number can be inferred automatically from the git history That's an interesting idea. If it was guaranteed that every merged PR would have the standardized commit message...

To ensure that filenames are easy to parse later, I'd suggest adding a check that the branch name not contain any dots: ```python branch = subprocess.check_output(["git", "branch", "--show-current"]).decode().strip() if '.'...

> To ensure that filenames are easy to parse later Then again, ```python parts = filename.split('.') username = parts[0] change_type = parts[-2] branch = '.'.join(parts[1:-2]) ``` so maybe it doesn't...

But yet again, what about slashes in branch names? Maybe it would be good to require that they use just alphanumerics and hyphens? Or do percent encoding, in order not...

Okay, there are a lot of different methods being considered here. For a separate project that I maintain, I am considering using percent-encoded branch names in the filenames, and using...

> This is potentially easier for contributors since it is not multiple files I guess I'd lean toward whatever makes things easiest for contributors, and I would agree with you...

> These expressions involving only a single radical and I are pretty reasonable and in some situations probably easier to work with or more natural than complex exponentials. How about...

I'm sorry I missed this issue. I do feel it would be worth considering #23589 again, as a way to give users better control over printing. In short, make expression...

@pavelvasev , can you say what are the `id`s of the endpoints of the edges that are getting the crazy routing highlighted in yellow? I'm trying to determine if this...

Although I don't understand the software nearly as well as @soerendomroes , I will continue to chime in, as I'm interested in understanding this problem. QUESTION: Among the following options,...