mapcrafter / mapcrafter/blockcrafter

Docker build automation

Open
#9 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
15
Forks
9
PR merge metrics
No merged PRs in 30d

Description

We have to make sure the docker builds are triggered after code is merged into `master`. It'd be useful to use/set tags as mentioned in issue #6.

Thanks @fredkilbourn for noticing!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the repository's existing Docker build setup and CI configuration, then read issue #6 for the intended tag behavior. Done means Docker builds are triggered after changes merge into master and the resulting images use the agreed tags.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.