Skip to content

Commit dea8775

Browse files
Add workflow used to automatically create GitHub releases
The new workflow uses a "RELEASE" file to create, when required, new release tags and GitHub releases. It uses the following GutHub action: https://github.com/pipe-cd/actions-gh-release --- With this in place, the release strategy would be to: - publish to npm locally. As part of publishing, the package's version will be stepped in package.json. Create a commit for that change and also add/update the RELEASE file (*) with corresponding tag. - push that commit for review to the GitHub project - The GitHub action will add a preview of the Github release to be created upon merging - once merged, the new tag and automatically-generated GitHub release will be created, that correspond to the published npm pacakge (*) https://github.com/pipe-cd/actions-gh-release#usage Signed-off-by: Marc Dumais <[email protected]>
1 parent 5cb94e4 commit dea8775

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

.github/workflows/gh-release.yml

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
on:
2+
push:
3+
branches:
4+
- main
5+
paths:
6+
- 'RELEASE'
7+
pull_request:
8+
types: [opened, synchronize]
9+
branches:
10+
- main
11+
paths:
12+
- 'RELEASE'
13+
14+
jobs:
15+
gh-release:
16+
runs-on: ubuntu-latest
17+
steps:
18+
- uses: actions/checkout@v3
19+
with:
20+
fetch-depth: 0
21+
- uses: pipe-cd/[email protected]
22+
with:
23+
release_file: 'RELEASE'
24+
token: ${{ secrets.GITHUB_TOKEN }}

0 commit comments

Comments
 (0)