I’m not native, but have lived in Philly. The bell peppers bother me. Wiz, American, provolone, or Swiss all are pretty common in my experience. As is no cheese at all, which this appears to be. But then it’s not a cheesesteak, it’s a steak.

There’s not a complete sentence after the period, so no.

I hadn’t seen the spam myself, but I think it’s to do with this.

In case you missed the second image on the original post, that text is in this pattern in glow in the dark thread

I’m guessing you don’t mean commits that actually bring updates from a different branch in? I’m responsible for a bunch of commits that catch my feature branch up to main and a couple that bring my branches into main.

If we were working on the same project, what would you want to see for those? This is hosted on a private gh repo, but it’s a small shop and we were working on a tight deadline for an MVP release and were not using PRs for the stuff I was working on.

The boss (co-owner of the business) is the Sr dev on the project and until recently was the only sr dev in the whole shop. I actually don’t think he has experience with using git in a team context.

One of my other tasks is working on internal docs (which didn’t exist before I joined the team) that would include git best practices for branching strategies and commit messages, so I’m interested in what folks who have more experience than I do would like to see as I try to nudge the team practices.

Git won’t let the second person push if their commit history doesn’t line up with the origin branch.

It should be trivial to do a git pull --rebase to move your new commit after the upstream version, but as far as I can tell, no one on my current project remembers this (or perhaps they’re using gui tools or something). Our log is full of “merge origin/main onto main”.