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

Automate release and deployment #9

Open
stieg opened this issue Nov 1, 2020 · 3 comments
Open

Automate release and deployment #9

stieg opened this issue Nov 1, 2020 · 3 comments

Comments

@stieg
Copy link
Contributor

stieg commented Nov 1, 2020

Need to automate this deployment to make project easier to maintain. Ideally deployment would happen if we pushed a signed tag to the main branch. However there is the issue where the updated code has to be available for GitHub actions to use (I am not aware if it being able to use a build artifact at this time... I hope there is a way it can). Ticket tracks figuring out best way to automate this release process and keep it sane.

@spyoungtech
Copy link

spyoungtech commented Nov 20, 2020

Could consider using the create-release action, which should do the trick.

A trigger condition like this should get what you want.

on:
  push:
    tags:
      - 'v[0-9]+.[0-9]+.[0-9]+' # Push events to matching semver-like tags, i.e. v1.0.0, v20.15.10
    branches-ignore:
      - '!main'  # not sure if this works or is needed, but would avoid accidentally(?) creating a release from another branch

New GitHub Actions versions get released to the marketplace upon creation of a release, so, this should work for that use case.

@stieg
Copy link
Contributor Author

stieg commented Nov 20, 2020

@spyoungtech Thanks for pointing that out. Will look into it.

@rinchsan
Copy link
Contributor

rinchsan commented Jan 30, 2021

I'm using https://github.com/release-drafter/release-drafter to automatically create a draft release when PR is merged.
Last thing you have to do manually is to publish the draft release whenever you want.
Semantic version is also decided by release-drafter automatically.

You can activate release-drafter in GitHub Actions (example) .

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

3 participants