create-release icon indicating copy to clipboard operation
create-release copied to clipboard

An Action to create releases via the GitHub Release API

Results 56 create-release issues
Sort by recently updated
recently updated
newest added

The example use of create-release in the README contains this line: ``` tag_name: ${{ github.ref }} ``` Should a user leave this in while having actions set to trigger for...

ref #124 Changes: * added tag_name to outputs * added secondary test for a different version * Updated README.md to include the output

It took a few attempts to find a solution to get a version # to tag the releases with. In my case I have a VERSION file containing the version...

I want to use the tag_name (short form, as in create_release.js - const tag = tagName.replace('refs/tags/', ''); in downstream steps in the workflow. e.g. to brand version into source files...

hi everybody, not sure if i misunderstand something. but do you have any idea how to prevent the action from including the .github/workflows/ directory into the release-files? i am using...

Hi! in the README.md, in the [Example Workflow](https://github.com/actions/create-release#example-workflow---create-a-release) section, it is mentioned that: > This will create a Release, as well as a release event, which could be handled by...

Here's the workflows, which should run when tag event happen, but I accidentally comments out those filter, so it create a release tag with name (refs/heads/master) , which cause later...

When automatically creating releases from tags, it would be great to have an option to populate the release name and body from the body of annotated tags, in a similar...

The text passed to `body` or `body_path` shows up on on the Releases page in plain text. I would expect it to be rendered in markdown (at least optionally). In...

**Expected behaviour** Tags the last commit **Actual behaviour** The commit before the last commit is tagged **Context** I have a workflow that makes a new commit & push and then...