Can we do better than this? (media.piefed.social)

submitted 1 week ago by lol_idk@piefed.social to c/voyagerapp@lemmy.world

6 comments fedilink hide all child comments

Like even a little description?

top 6 comments

sorted by: hot top controversial new old

[-] MagicShel@lemmy.zip 7 points 1 week ago* (last edited 1 week ago)

I've never looked at the code base and I could make a reasonable guess as to what it's about. I'm guessing it has to do with pasting a fediverse link into a post and making it point to the actual instance instead of the federated link.

I could be wrong but it looks like it would make sense to the maintainers of the code.

Or am I just missing a joke here?

Edit: sorry if this comes across dickish. I don't have context for the question. It looks frankly like a very efficient use of words — I'm a little bit in awe. Take away one word and it would be gibberish to me. My own commit messages are not nearly as efficient.

[-] toofpic@lemmy.world 1 points 1 week ago

The fact that you're asking proves the description is bad. URLs? "Fixed: when a URL is passed to AAA, BBB should be CCC, but it is DDD instead". "Stupid* descriptive commit messages are unbeatable. You might as well copy the whole bug description if it's not super long and was formulated by a person used to describe things (so, any good QA)

[-] CTDummy@piefed.social 3 points 1 week ago* (last edited 1 week ago)

I think the description is sufficient. As long as the dev and contributors know what it’s referring to. Isn’t this app mostly worked on by one person? I think people complaining about short action descriptions or calling them stupid is a bit excessive. Unless both you and the OP are looking to contribute?

[-] lol_idk@piefed.social 0 points 1 week ago

So users don't care or deserve to understand what's being fixed?

[-] CTDummy@piefed.social -1 points 1 week ago

Did I say that? GitHub action descriptions isn’t really an avenue to communicate with users.

[-] KairuByte@lemmy.dbzer0.com 2 points 1 week ago

I believe this is an automated TestFlight push. Meaning there’s no direct user involvement, and it’s simply pulling commit messages.

I’ve always treated the voyager TestFlight as a nightly build. Use the app as per normal, report any issues you find. You re not explicitly being asked to test something in particular (despite what the TestFlight prompts suggest.)