+ [2020-06-02T23:51:38Z] nedbat cos: perhaps they say origin/the-branch-name ?
+ [2020-06-02T23:52:17Z] cos yes they do. I guess you're saying this branch may hve been deleted from origin while the rest were not? (which would also be really puzzling)
+ [2020-06-02T23:52:52Z] nedbat cos: no. you deleted them locally. origin still has them (probably). You still have your local idea of origin's branch. that's what "origin/the-branch" means.
+ [2020-06-02T23:55:27Z] cos I deleted all these branches locally, yes. So why would origin still have most of them, but be missing that one where the tag is? Maybe I can figure it out but it seems puzzling.
+ [2020-06-02T23:58:40Z] cos oh well, I'll stop trying to understand this now that I know I can use --all to see all the tags. I guess what I really want is to show all commits merged into master, that are more recent than a particular tag, even if that tag isn't in master.

message no. 181595

Posted by peepsalot in #github at 2020-06-02T17:25:05Z

is there any possibly solution for uploading CI artifacts to a project's own web server? we currently have a solution that can upload test results, but it only functions for PRs created from the main repo. PRs from forks of the project can't get permission unless we share secret keys with said forks?
+ [2020-06-03T00:00:04Z] cos I guess I could do that in two steps, first --all and capture the hash for the tag, then git log hash..HEAD
+ [2020-06-03T00:09:36Z] nedbat cos: hash..HEAD won't do what you want if they aren't on the same line
+ [2020-06-03T00:11:16Z] nedbat cos: also, you can get the hash for a tag with: git rev-parse tagname
+ [2020-06-03T00:30:31Z] cos oh that's useful.
+ [2020-06-03T00:31:07Z] cos and I think that is what I want - though git is convoluted enought that if it's not what I want it may take a long time to figure it out :/