As an aside, God, Azure DevOps, what a total pile of crap that product is

My "favourite" restriction that an Azure DevOps PR description is limited to a pathetic 4000 characters.

OkayPhysicist 6 hours ago | parent | next [-]

My favourite restriction is the fact that colored text doesn't work in dark mode. Why? Because whatever intern they had implement dark mode didn't understand how CSS works, and just slapped !important on all the style changes that make dark mode dark, and thus overwrite the color data.

I ended up writing a browser extension for my team to fix it, because the boss loved to indicate stuff with red/green text.

▲

dylan604 8 hours ago | parent | prev | next [-]

Amazon's deprecated CodeCommit is limited to 150 chars like it's an old SMS or Tweet.

▲

heartbreak 2 hours ago | parent | next [-]

Surprisingly they un-deprecated CodeCommit recently.

https://aws.amazon.com/blogs/devops/aws-codecommit-returns-t...

▲

jbreckmckye 8 hours ago | parent | prev [-]

Ha! Nice. I never worked with CodeStar / CodeCommit. Was it pretty bad?

	▲	dylan604 7 hours ago \| parent [-]
		That's going to depend on each user's demands. The PR message limit is the biggest pain for me. I don't depend on the UI very often. I'm not trying to do any CI/CD nonsense. I just use it as a bog standard git repo. When used as that, it works just fine for me

▲

noodlesUK 8 hours ago | parent | prev | next [-]

It shows you the level of quality to expect from a Microsoft flagship cloud product...

▲

jbreckmckye 8 hours ago | parent [-]

So I work for a devtools vendor (Snyk) and 6 months ago I signed into Azure DevOps for the first time in my life

I couldn't believe it. I actually thought the product was broken. Just from a visual perspective it looked like a student project. And then I got to _using_ the damn thing

▲

noodlesUK 8 hours ago | parent [-]

It's also completely unloved. Even MSFT Azure's own documentation regularly treats it as a second class citizen to GitHub. I have no idea why they don't just deprecate the service and officially feature freeze it.

Honestly that's the case with a lot of Azure services though.

▲

stackskipton 6 hours ago | parent | next [-]

Someone mentioned the boards but Pipelines/Actions are not 100% compliant.

My company uses Azure DevOps for a few things and any attempt to convert to GitHub was quickly abandoned after we spent 3 hours trying to get some Action working.

However, all usability quarks aside, I actually prefer these days since Microsoft doesn't really touch it and it just sits in corner doing what I need.

▲

easton 8 hours ago | parent | prev [-]

It's the boards. GitHub issues doesn't let you do all the arcane nonsense Azure DevOps' boards let you do.

▲

bigfudge 5 hours ago | parent [-]

Isn’t that a feature?

	▲	easton 3 hours ago \| parent [-]
		A feature for devs, but I have often been told management is paid by the required field on tickets.

▲

tibbar 8 hours ago | parent | prev | next [-]

You would kind of expect with the pressure of supporting OpenAI and GitHub etc. that Azure would have been whipped into shape by now.

	▲	semiquaver 8 hours ago \| parent [-]
		AZDO has been in KTLO maintenance mode for years.

▲

yoyohello13 5 hours ago | parent | prev [-]

My favorite is that it doesn't support ed25519 ssh keys.