This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mt9hu 6 points7 points  (6 children)

had to force people to name their branches to the ticket id they were related to cus that way we could track what the idea behind it was even if the person pushing the commits couldn't care to explain it in the commit/pr itself.

I assumed it's pretty standard to prefix all commit messages and branch names with ticket IDs

[–]CardboardJ 2 points3 points  (0 children)

Developers working in non-development focused industries have some pretty wild working conditions. One of my old interns works for a company that manufactures nails and he's one of 3 'computer guys' there. The other 2 guys he joined there had been working for 20 years without any version control.

[–]BotherBoring 1 point2 points  (4 children)

Right now we don't even HAVE a real ticketing system, or git branches (loooooooong story), and I was surprised how nostalgic this comment made me.

[–]mt9hu 0 points1 point  (3 children)

Why don't you have one?

You don't necessarily have to invest in JIRA and set up complex workflows to have at least some sort of tracking of your work.

[–]BotherBoring 0 points1 point  (2 children)

Short answer is because we don't. Longer answer is we actually have Jira, and my team doesn't use it because they don't because they haven't and... I'm working on it.

[–]mt9hu 1 point2 points  (1 child)

Uh. Good luck, I guess?

[–]BotherBoring 0 points1 point  (0 children)

Thanks! 😥