dev branch becomes development

Default the component branches in Dockerfile to be `development` (might change to master after full v6 release)

Signed-off-by: Adam Warner <me@adamwarner.co.uk>
This commit is contained in:
Adam Warner
2024-09-02 21:46:22 +01:00
parent 7a33749f4e
commit 32c57752cf
7 changed files with 29 additions and 46 deletions

View File

@@ -1,4 +1,4 @@
`{Please select 'base: dev' as target branch above! (you can delete this line)}`
`{Please select 'base: development' as target branch above! (you can delete this line)}`
<!--- Provide a general summary of your changes in the Title above -->

View File

@@ -7,7 +7,7 @@ updates:
interval: "weekly"
day: saturday
time: "10:00"
target-branch: dev
target-branch: development
reviewers:
- "pi-hole/docker-maintainers"
- package-ecosystem: "docker"
@@ -16,7 +16,7 @@ updates:
interval: "weekly"
day: saturday
time: "10:00"
target-branch: dev
target-branch: development
reviewers:
- "pi-hole/docker-maintainers"
- package-ecosystem: pip
@@ -26,35 +26,6 @@ updates:
day: saturday
time: "10:00"
open-pull-requests-limit: 10
target-branch: dev
target-branch: development
reviewers:
- "pi-hole/docker-maintainers"
# Maintain dependencies for GitHub Actions development-v6
- package-ecosystem: "github-actions"
directory: "/"
schedule:
interval: "weekly"
day: saturday
time: "10:00"
target-branch: development-v6
reviewers:
- "pi-hole/docker-maintainers"
- package-ecosystem: "docker"
directory: "/src/"
schedule:
interval: "weekly"
day: saturday
time: "10:00"
target-branch: development-v6
reviewers:
- "pi-hole/docker-maintainers"
- package-ecosystem: pip
directory: "/test"
schedule:
interval: weekly
day: saturday
time: "10:00"
open-pull-requests-limit: 10
target-branch: development-v6
reviewers:
- "pi-hole/docker-maintainers"
- "pi-hole/docker-maintainers"

View File

@@ -4,7 +4,7 @@ on:
- cron: "0 5 * * *"
push:
branches:
- dev
- development
release:
types: [published]
@@ -12,6 +12,7 @@ on:
env:
dockerhub: ${{ secrets.DOCKERHUB_NAMESPACE }}/pihole
ghcr: ghcr.io/${{ github.repository_owner }}/pihole
components_branch: ${{ startsWith(github.ref, 'refs/tags/') && 'master' || 'development' }}
jobs:
build:
@@ -39,7 +40,7 @@ jobs:
if: github.event_name == 'schedule'
uses: actions/checkout@v4
with:
ref: dev
ref: development
- name: Docker meta
id: meta
@@ -80,7 +81,11 @@ jobs:
platforms: ${{ matrix.platform }}
build-args: |
PIHOLE_DOCKER_TAG=${{ steps.meta.outputs.version }}
alpine_version=${{ matrix.alpine_version }}
alpine_version=${{ matrix.alpine_version }}
FTL_BRANCH=${{ env.components_branch }}
CORE_BRANCH=${{ env.components_branch }}
WEB_BRANCH=${{ env.components_branch }}
PADD_BRANCH=${{ env.components_branch }}
labels: ${{ steps.meta.outputs.labels }}
outputs: |
type=image,name=${{ env.dockerhub }},push-by-digest=true,name-canonical=true,push=true
@@ -108,8 +113,15 @@ jobs:
- build
steps:
- name: Checkout Repo
if: github.event_name != 'schedule'
uses: actions/checkout@v4
- name: Checkout dev branch if scheduled
if: github.event_name == 'schedule'
uses: actions/checkout@v4
with:
ref: development
- name: Download digests
uses: actions/download-artifact@v4
with:

View File

@@ -13,6 +13,6 @@ jobs:
- name: Checkout
uses: actions/checkout@v4
- name: Opening pull request
run: gh pr create -B dev -H master --title 'Sync master back into development' --body 'Created by Github action' --label 'internal'
run: gh pr create -B development -H master --title 'Sync master back into development' --body 'Created by Github action' --label 'internal'
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

View File

@@ -2,8 +2,8 @@
Please review the following before opening a pull request (PR) to help your PR go smoothly:
* Code changes go to the `dev` branch first
* To ensure proper testing and quality control, target any code change pull requests against `dev` branch.
* Code changes go to the `development` branch first
* To ensure proper testing and quality control, target any code change pull requests against `development` branch.
* Make sure the tests pass
* Take a look at [TESTING.md](test/TESTING.md) to see how to run tests locally so you do not have to push all your code to a PR and have GitHub Actions run it.

View File

@@ -175,9 +175,9 @@ The Date-based (including incremented "Patch" versions) do not relate to any kin
| `latest` | Always latest release |
| `2022.04.0` | Date-based release |
| `2022.04.1` | Second release in a given month |
| `dev` | Similar to `latest`, but for the development branch (pushed occasionally) |
| `development` | Similar to `latest`, but for the development branch (pushed occasionally) |
| `*beta` | Early beta releases of upcoming versions - here be dragons |
| `nightly` | Like `dev` but pushed every night and pulls from the latest `development` branches of the core Pi-hole components (Pi-hole, web, FTL) |
| `nightly` | Like `development` but pushed every night and pulls from the latest `development` branches of the core Pi-hole components (Pi-hole, web, FTL) |
## Upgrading, Persistence, and Customizations

View File

@@ -5,11 +5,11 @@ FROM alpine:${alpine_version} AS base
# https://docs.docker.com/engine/reference/builder/#automatic-platform-args-in-the-global-scope
ARG TARGETPLATFORM
ARG WEB_BRANCH="development-v6"
ARG CORE_BRANCH="development-v6"
ARG FTL_BRANCH="development-v6"
ARG WEB_BRANCH="development"
ARG CORE_BRANCH="development"
ARG FTL_BRANCH="development"
ARG PIHOLE_DOCKER_TAG="dev-localbuild"
ARG PADD_BRANCH="PADD_FTLv6"
ARG PADD_BRANCH="development"
ENV DNSMASQ_USER=pihole
ENV FTL_CMD=no-daemon