Docker image build Action #72

Merged
bluikko merged 3 commits from github-action-docker into master 2021-10-10 21:29:03 +08:00
bluikko commented 2021-07-10 14:55:57 +08:00 (Migrated from github.com)

A simple proof of concept for building docker image.

It should also push the image to some public registry.

A simple proof of concept for building docker image. It should also push the image to some public registry.
bluikko commented 2021-07-19 09:22:47 +08:00 (Migrated from github.com)

For #70.

For #70.
annikahannig commented 2021-10-10 21:28:51 +08:00 (Migrated from github.com)

I wonder if there is a way to build the develop branch to, but tag this with idk alicelg-dev oder something...

I wonder if there is a way to build the develop branch to, but tag this with idk alicelg-dev oder something...
bluikko commented 2021-10-11 11:15:43 +08:00 (Migrated from github.com)

I wonder if there is a way to build the develop branch to, but tag this with idk alicelg-dev oder something...

Yes, sure. The 2 lines to change (depending if you want to run it for all pushes or just some):

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

The documentation is at https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows or if you figure out and list the exact scenarios where image should be built then I can update it too.

> I wonder if there is a way to build the develop branch to, but tag this with idk alicelg-dev oder something... Yes, sure. The 2 lines to change (depending if you want to run it for all pushes or just some): ```yaml on: push: branches: [ master ] pull_request: branches: [ master ] ``` The documentation is at https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows or if you figure out and list the exact scenarios where image should be built then I can update it too.
Sign in to join this conversation.
No description provided.