search

repo-sync / github-sync

⤵️ A GitHub Action for syncing current repository with remote
https://github.com/marketplace/actions/github-repo-sync
MIT License
393 stars 103 forks source link

feat: hide upstream branches from logs #33

Closed wei closed 4 years ago

wei commented 4 years ago

Fixes #32

zeke commented 4 years ago

That was quick!

zeke commented 4 years ago

What is the process for creating a new release?

wei commented 4 years ago

@zeke Now that we're using the brand new GitHub Container Registry, release requires 3 steps

Let's say we're releasing v2.2.2

  1. Edit actions.yml in master and update the docker image version to v2.2.2, commit with message release: v2.2.2
  2. Go to new release to publish a new release with v2.2.2 @ master, use the feature commit message for the release title

  3. Once v2.2.2 is verified, we'll force push a v2 tag to match v2.2.2

    git checkout master
git pull  # Make sure you're on the latest commit
git tag v2 -f
git push origin v2 -f

Step 1 is required because there is no automatic way of linking an actions release to a docker image release. We can definitely automate some of the steps in the future using actions.

wei commented 4 years ago

Pushing tags will automatically trigger the deploy workflow which builds and pushes docker images at https://github.com/orgs/repo-sync/packages/container/package/github-sync