Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action successful but now showing up under assets in release #22

Open
nnofel opened this issue Jul 31, 2020 · 6 comments
Open

Action successful but now showing up under assets in release #22

nnofel opened this issue Jul 31, 2020 · 6 comments

Comments

@nnofel
Copy link

nnofel commented Jul 31, 2020

The action shows that it is finished successfully but the asset uploaded doesn't show under the Release

@svenstaro
Copy link
Owner

Does the log say anything?

@nnofel
Copy link
Author

nnofel commented Jul 31, 2020

Screenshot 2020-07-31 at 16 01 14

@svenstaro
Copy link
Owner

Did the release already exist?

@nnofel
Copy link
Author

nnofel commented Aug 4, 2020

@svenstaro yes it did. In fact my workflow gets triggered on the create release event.

@mcaceresb
Copy link

@svenstaro I am having this exact issue as well (same log). The relevant section in my file:

      - uses: svenstaro/upload-release-action@v2
        with:
          repo_token: ${{ secrets.COMPILE_TOKEN }}
          file: src/build/file
          tag: ${{ github.ref }}
          overwrite: true

@iwishiwasaneagle
Copy link

Same issue on my end

      - name: Upload the release
        uses: svenstaro/upload-release-action@v2
        with:
          repo_token: ${{ secrets.GITHUB_TOKEN }}
          tag: ${{ github.ref }}
          file: main.pdf
          overwrite: true
          asset_name: "${{needs.setup-envs.outputs.tag-name}}.pdf"
          release_name: "${{needs.setup-envs.outputs.tag-name}}"
          body: "${{ needs.setup-envs.outputs.release_body }}"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants