Skip to content
This repository has been archived by the owner on Oct 25, 2022. It is now read-only.

Plugin GitReleases fails #227

Closed
nils-a opened this issue Nov 17, 2020 · 2 comments · Fixed by #228
Closed

Plugin GitReleases fails #227

nils-a opened this issue Nov 17, 2020 · 2 comments · Fixed by #228

Comments

@nils-a
Copy link
Contributor

nils-a commented Nov 17, 2020

My build log looks like this:

Commiting
[test/set-env 5b3bd9d] AU: 1 updated - cleanmgrplus [skip ci] https://gist.github.com/be944da6cbb50300f2e3114bf35724a0/6850824cd899db1bd618afa98268a18fe5da9e14
 2 files changed, 4 insertions(+), 4 deletions(-)
Pushing changes

Running GitReleases
Creating the new release cleanmgrplus-1.36.1141...
  ERROR:  
    {"message":"Validation Failed","errors":[{"resource":"Release","code":"custom","field":"tag_name","message":"tag_name is not a valid tag"},{"resource":"Release","code":"custom","message":"Published releases must have a valid tag"},{"resource":"Release","code":"invalid","field":"target_commitish"}],"documentation_url":"https://docs.github.com/rest/reference/repos#create-a-release"}

I guess at least part of the error is me not having a master branch while GitReleases,ps1 expects one to always be there.
https://github.com/majkinetor/au/blob/master/AU/Plugins/GitReleases.ps1#L51 reads:

"target_commitish" = "master" 

While GitReleases is not new, I have never noticed the plugin to fail. (However, no releases were created, either.)

@majkinetor
Copy link
Owner

So if you change master to what you have, does it work ?

@nils-a
Copy link
Contributor Author

nils-a commented Nov 17, 2020

majkinetor added a commit that referenced this issue Nov 17, 2020
replaced the fixed target_commitish of "master"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants