Release assets not appearing #25347

andymantell · 2020-06-15T12:29:02Z

andymantell
Jun 15, 2020

Hi,

I have a Github action setup to create a release and upload binaries to it, however I am experiencing some odd behaviour. If I view the release on the following URL I do not see any assets apart from the source code:

https://github.com/andymantell/govuk-frontend-diff/releases/tag/v0.1-alpha-4

This is the URL that I can reach by clicking through the releases section in the Github UI. However, when the action has run I also receive an email from github saying that a new release has been created at:

https://github.com/andymantell/govuk-frontend-diff/releases/tag/refs/tags/v0.1-alpha-4

This one has all the artifacts that I am expecting to see.

As far as I can see, they are one and the same release. But they appear to have different URLs (One has an additional refs/tags section in it.

I don’t quite understand what’s going on here. Can anyone shed any light on this?

Thanks,

Andy

Answered by weide-zhou

Jun 16, 2020

Hi @andymantell,

Glad to see you in Github Community Forum!
To add assets to an existing release, please use ‘edit’ instead of ‘create’ for command ‘hub release’.
Option ‘create’ will create a GitHub release for the specified TAG name. If git tag TAG does not exist, it will be created at TARGET (default: current branch).
Please fix code as below:

      - name: Attach binaries to release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          set -x
          assets=()
          for asset in ./bin/*; do
            assets+=("-a" "$asset")
          done
          githubref=${{ github.ref }}   # get the github.ref value
          hub release edit "${assets[…

View full answer

weide-zhou · 2020-06-16T03:38:41Z

weide-zhou
Jun 16, 2020

Hi @andymantell,

Glad to see you in Github Community Forum!
To add assets to an existing release, please use ‘edit’ instead of ‘create’ for command ‘hub release’.
Option ‘create’ will create a GitHub release for the specified TAG name. If git tag TAG does not exist, it will be created at TARGET (default: current branch).
Please fix code as below:

      - name: Attach binaries to release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          set -x
          assets=()
          for asset in ./bin/*; do
            assets+=("-a" "$asset")
          done
          githubref=${{ github.ref }}   # get the github.ref value
          hub release edit "${assets[@]}" -m "${githubref##*/}" "${githubref##*/}"   # specify tag name not the github.ref here.

It works on my side. Please check my workflow here.

Thanks

0 replies

andymantell · 2020-06-16T07:45:31Z

andymantell
Jun 16, 2020
Author

Thanks @weide-zhou! I have made the changes you suggest and it’s now working perfectly.

Thankyou very much for the quick response, very much appreciated.

github.com/andymantell/govuk-frontend-diff

Fix release.yml to make sure binaries get associated with the releases

<div class="github-info">
  <div class="date">
    committed <span class="discourse-local-date" data-format="ll" data-date="2020-06-16" data-time="07:34:29" data-timezone="UTC">07:34AM - 16 Jun 20 UTC</span>
  </div>

  <div class="user">
    <a href="https://github.com/andymantell" target="_blank" rel="nofollow noopener">
      <img alt="andymantell" src="https://user-images.githubusercontent.com/134642/181090559-f9d333a3-8cfb-45e5-bd24-1214c7d9b07a.jpeg" class="onebox-avatar-inline" width="20" height="20">
      andymantell
    </a>
    
  </div>

  <div class="lines" title="changed 1 files with 2 additions and 1 deletions">
    <a href="https://github.com/andymantell/govuk-frontend-diff/commit/f3c246c556a69a7daa529d9d11ef1ebe0240a0e5" target="_blank" rel="nofollow noopener">
      <span class="added">+2</span>
      <span class="removed">-1</span>
    </a>
  </div>
</div>

See https://github.community/t/release-assets-not-appearing/118148
Co-authored-by: weide-zhou <weide-zhou@outlook.com>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Release assets not appearing #25347

{{title}}

Replies: 2 comments

{{title}}

{{title}}

Fix release.yml to make sure binaries get associated with the releases

Select a reply

GitHub Community

Release assets not appearing #25347

andymantell Jun 15, 2020

Replies: 2 comments

weide-zhou Jun 16, 2020

andymantell Jun 16, 2020 Author

Fix release.yml to make sure binaries get associated with the releases

andymantell
Jun 15, 2020

weide-zhou
Jun 16, 2020

andymantell
Jun 16, 2020
Author