release-action | An action which manages a github release | Continous Integration library
kandi X-RAY | release-action Summary
kandi X-RAY | release-action Summary
This action will create a GitHub release and optionally upload an artifact to it.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of release-action
release-action Key Features
release-action Examples and Code Snippets
Community Discussions
Trending Discussions on release-action
QUESTION
I'm using the github actions release-action@v1
in my workflow, and it's not generating artifacts after signing the app and building the apk and app bundle.
I created a tag before pushing to the repository, but the action is still not working.
I think it's because am not passing a commit
to the workflow.
What do I need to do there?
Error: ...ANSWER
Answered 2022-Mar-15 at 12:47The action documentation states that:
You must provide a tag either via the action input or the git ref (i.e push / create a tag). If you do not provide a tag the action will fail.
Moreover, the tag input states:
tag: An optional tag for the release. If this is omitted the git ref will be used (if it is a tag).
Your issue is probably related to the push
trigger you set in your workflow file, as it will not generate any git ref tag. And as you're not using the action tag input, the action can't identify the tag to use to generate the release.
You have 2 options here:
- Remove the on push trigger. For the workflow, and consequently the action, only run if a tag is present.
- Add the tag input to the action with the
artifacts
and thetoken
inputs you're already using.
QUESTION
I am trying to build a simple "Hello World" Rust program and create a GitHub release using an artifact of the build process. The toolchain being used is stable-x86_64-unknown-linux-gnu
, which has no problems when running cargo build
or cargo run
locally. The release itself, along with the produced binary, can be found here. The GitHub Action logs can be found here.
The action is able to create the release, but the produced binary does not execute on my system (Ubuntu 21.10 impish). In the following commands, the name of the downloaded binary is x86_64-unknown-linux-gnu
.
ANSWER
Answered 2022-Jan-08 at 21:50I found a solution. Apparently, UPX somehow breaks the Linux executable. However, when I tried to build a Windows executable, UPX still worked fine. In order to fix my GitHub Action workflow, I made the following changes:
QUESTION
gone through a variety of the articles, and none seem to "Work". In particular, 2021r1, not getting ANY of the PXTrace statement in the output
Challenge: Static method of the graph directly called from ARPaymentEntry, and 4-5 overloads (From .\App_Data\CodeRepository\PX.Objects\AR\ARDocumentRelease.cs) Eventually ends up calling a single method within that graph, starting with "public static void ReleaseDoc(" No clear place to add a delegate, though that seems the "most correct" method (E.g. question 37262565, comment from cbetabeta) - Yet the initialize event doesn't appear to be firing (possibly JIT optimization? Direct call into static method doesn't really need the class to be instantiated, I'd guess)
Also need a complete solution - e.g. Must handle the call from Payment Entry as well as from AR Document Release process
Sample Code:
...ANSWER
Answered 2021-Jun-02 at 12:54I think its the namespace that is the issue:
QUESTION
I'm currently using the Release Drafter workflow that creates a draft release whenever a PR is merged into the develop
branch (staging). This creates a great draft but now I'm wanting to have it get published when develop is merged into master. When that takes place I need to update the release name and tag before publishing. Then send out a notification in our slack engineering channel.
What I can do:
- Setup the action on push into master.
- Get the latest draft release and then use that id as a ref.
- Publish using eregon/publish-release action.
- Send the slack message
What I missing:
- An Action that I can pass the release id and update the tag and name.
The name and tag will be the current date %Y.%m%.d-%H:%M
Here is the action YML I have created so far
...ANSWER
Answered 2021-May-17 at 15:55You can add a step that updates the release draft using Github's REST API:
QUESTION
I'm using the following Actions YAML to try to build an Android APK from a Flutter app:
...ANSWER
Answered 2020-Dec-25 at 20:29As per the notes you either need to specify an existing tag or specify a branch or commit for the commit
input of the action, based on which a tag will be created:
- You must provide a tag either via the action input or the git ref (i.e push / create a tag). If you do not the action will fail.
- If the tag of the release you are creating does not exist yet, you should set both the
tag
andcommit
action inputs.commit
can point to a commit hash or a branch name (ex -main
).
from https://github.com/ncipollo/release-action#notes
Using the following will give you a new version tag with every run, where the last place of the version is incremented for every run.
QUESTION
I am using the Datatable as a component so that I can use it in all the templates I have. I have the following files :
table.component.ts
...ANSWER
Answered 2020-Aug-31 at 19:21There seems to be two different problems;
The second error DataTables warning: table id=releaseDatatable - Cannot reinitialise DataTable
indicates that you are using more than one dataTable with the same id.
This error is most likely being experienced when you load more than one dataTable component.
To solve this you should generate a way of identifying each unique data table eg declare a variable counter and call $('#releaseDatatable' + counter).DataTable().destroy();
when getting then dataTable while binding to [attr.id]='"releaseDatatable" + counter'
in the html
The First error will be attributed to the code below
QUESTION
Currently I have the following code:
...ANSWER
Answered 2020-Apr-30 at 01:04As you've implied, you can't limit the scope of a personal access token to different scopes for different repos. Theres a few ways of doing this.
Intermediate, public storage
The first is to upload the artifacts to an intermediate place, accessible from anywhere, e.g. Dropbox, Docker Hub, etc. Then you can manually trigger a github action in your public repo to pull this artifact back down and create a release from it. To manually trigger this action you could use the repository_dispatch
event either using cURL / postman locally (with an access token auth bearer) or using something like https://www.actionspanel.app/ which is a github app which allows you to manually trigger github actions using repository_dispatch
, with parameters so your download link would be a parameter.
Personal access token
The simplest option is still a personal access token though. Your workflow above has repo_token: XXXXXXXXX
which makes me wonder if you know about github secrets? Ideally this token would be stored in a secret then accessed using ${{ secrets.BRANDONS_TOKEN }}
. I would ask why you are worried about a personal access token. If you use github secrets and are careful about the 3rd party code you pass the token to (you may not want to simply pass your token to @master
, for example), it should be fine.
GitHub Apps & Webhooks
GitHub apps or webhooks would be another way, you can authenticate those on a per-person basis and per-repo basis but you'd need an application running online to receive and parse the messages and its quite a big piece of work.
(Probably not) GitHub Deploy Keys
Another thing to be aware of is Github Deploy Keys, you can use these to obtain read/write access to a single repository without an account attached. You would then store this deploy key in a secret in the settings of the other repo. However, I'm not sure you can trigger releases with deploy keys - they are not bound to an account so I'm unsure who's username would be visible on the release history.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install release-action
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page