https://github.com/hapag-lloyd/repository-template-docker

Template repository for Docker projects
https://github.com/hapag-lloyd/repository-template-docker

docker repository setup template

Last synced: about 6 hours ago
JSON representation

Template repository for Docker projects

• Host: GitHub
• URL: https://github.com/hapag-lloyd/repository-template-docker
• Owner: Hapag-Lloyd
• License: mit
• Created: 2024-05-06T15:08:12.000Z (6 months ago)
• Default Branch: main
• Last Pushed: 2024-10-24T16:35:22.000Z (14 days ago)
• Last Synced: 2024-10-26T12:55:39.974Z (12 days ago)
• Topics: docker, repository, setup, template
• Language: Dockerfile
• Homepage:
• Size: 29.3 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: .github/CODE_OF_CONDUCT.md
  • Codeowners: .github/CODEOWNERS

Awesome Lists containing this project

README

        
# Repository-Template-Docker

Template repository for Docker projects which are published on [DockerHub](https://hub.docker.com/r/hlag). Don't forget to update

the README.md file with the project information and initially run

```shell

git checkout main

.github/update_templates.sh

# strongly suggested!

pre-commit install -c .github/pre-commit-config.yaml

```

In case a major release is published on the Workflow-Template repository, run `.github/update_workflows.sh`. This creates a PR

with the changes in the workflows. Carefully check the changes and merge them into the `main` branch.

## Development

### Usage

This repository is used as a template repository for new Docker projects. Thus the newly created repository will have the same

structure and configurations as this one.

After merging into the `main` branch, use `.github/update_init_branches.sh` to merge these changes into the `init-` branches as

well.

### `init-` branches

The `init-` branches are used to initialize the project with the necessary files and configurations. Create them in this repository

and add a `pr-description.md` file with the description of the changes to be made. The first line contains the title of the PR

followed by a blank line and then the description.

Never merge these branches directly into the `main` branch.