Any way to manually set a git hash when deploying to GitHub?
Hi guys.
I have an app that automatically builds itself whenever I push.
It then uploads the binaries to a second GitHub repo, which creates an installer package on Windows.
This in turn uploads the installer package to the released page of the app's repo.
This works - the file is uploaded, however GitHub cannot provide a hash to go alongside of it. Basically, the file is updated, but the hash and date remain unchanged.
Is there any way to manually provide a git hash when deploying to a remote GitHub repository?
Thanks,
~Chris
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ilya Finkelshte... on 01 Apr, 2019 05:41 PM
Hi Chris,
Am I understanding you correctly that in your GItHub relieases deployment settings you have optional
Repository namesetting (repositoryin YAML) set to non-default repository, and want to be able to configuretarget_commitishwhen AppVeyor calls Create a release API?Ilya.
2 Posted by Chris Esposito on 01 Apr, 2019 08:23 PM
Yes, that's correct. I use a non-default `repository` setting.
I'm not sure that it's `target_commitish` that needs to change, though, as the API docs seem to suggest that it defaults to `master` (which is what I'd want things to be tagged as).
To clarify a bit, this YAML file here defines how the artifacts are uploaded to GitHub releases:
https://github.com/EspoTek/Labrador-win-builder/blob/master/.appveyor.yml
And here are the releases:
https://github.com/EspoTek/Labrador/releases
If you look at the `continuous-win32` release, it will say that it was released in November 2018, and the commit hash (and source) is from then too. However, the .exe itself is the latest version just released last night. It looks like the metadata is not being updated.
3 Posted by Ilya Finkelshte... on 02 Apr, 2019 02:09 AM
I believe this is expected behavior as you hard-coded the tag. In this case AppVeyor calls Edit a release API which does not update the SHA. If you add say
$(appveyor_build_version)to the tag name, it will display latest SHA in eachnew release.Ilya Finkelshteyn closed this discussion on 02 Jun, 2019 09:01 PM.