Like even a little description?
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.)
If its a commit message then not really you are rather limited on what you can put.
If it were a pr then as long as it makes sense to the maintainers, who cares?
Yes, the what to test file is release notes, they just are not populating them and are likely falling back to another string (the commit message)
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?
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)
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?
So users don’t care or deserve to understand what’s being fixed?
Did I say that? GitHub action descriptions isn’t really an avenue to communicate with users.


