From 856116f4a04953d88f2ad7c7eeebfbfb12727708 Mon Sep 17 00:00:00 2001 From: Jon Harper Date: Wed, 19 Mar 2025 15:27:31 +0100 Subject: [PATCH 1/3] README.md, add repo types and branching model Signed-off-by: Jon Harper --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index 91d5cbc..b3a06a4 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,15 @@ # github-ci Generic CI workflows for powsybl repositories + +There are dedicated workflows for each use cases: + +* backend-app: java project built with maven and audited by sonar, published as docker images. +* backend-lib: java project built with maven and audited by sonar, published as maven artifacts. +* base-docker-image: dockerfile project, published as docker images. +* frontend-app: node project built with npm and audited by sonar, published as docker images. +* frontend-lib: node project built with npm and audited by sonar, published as npm packages. + +Currently, the release/branching model differs between projects: +* backend-app, frontend-app, base-docker-image: can release at a recent commit on main. Releasing creates a branch there and patch releases can be done on these release branches. +* backend-lib: can release only the current tip of the main branch as a major or minor version. Patch releases can be done from release branches (needs admin right to create the release branch). +* backend-app: can release only the current ti of the main branch as a major or minor or patch version. From d960a85f0ec1e95342b29144babd2898323b0d7f Mon Sep 17 00:00:00 2001 From: Jon Harper Date: Thu, 20 Mar 2025 12:27:56 +0100 Subject: [PATCH 2/3] Update README.md Co-authored-by: Olivier Perrin Signed-off-by: Jon Harper --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b3a06a4..2ca03c9 100644 --- a/README.md +++ b/README.md @@ -12,4 +12,4 @@ There are dedicated workflows for each use cases: Currently, the release/branching model differs between projects: * backend-app, frontend-app, base-docker-image: can release at a recent commit on main. Releasing creates a branch there and patch releases can be done on these release branches. * backend-lib: can release only the current tip of the main branch as a major or minor version. Patch releases can be done from release branches (needs admin right to create the release branch). -* backend-app: can release only the current ti of the main branch as a major or minor or patch version. +* backend-app: can release only the current tip of the main branch as a major or minor or patch version. From ecb9e48b16dc67719610487a4416977857cd587f Mon Sep 17 00:00:00 2001 From: HARPER Jon Date: Fri, 21 Mar 2025 13:49:20 +0100 Subject: [PATCH 3/3] document permissions --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 2ca03c9..d793fe2 100644 --- a/README.md +++ b/README.md @@ -13,3 +13,10 @@ Currently, the release/branching model differs between projects: * backend-app, frontend-app, base-docker-image: can release at a recent commit on main. Releasing creates a branch there and patch releases can be done on these release branches. * backend-lib: can release only the current tip of the main branch as a major or minor version. Patch releases can be done from release branches (needs admin right to create the release branch). * backend-app: can release only the current tip of the main branch as a major or minor or patch version. + +For release-frontend-lib, we require in the caller workflow +```yaml +permission: + contents: write # for creating github releases + id-token: write # for adding npm provenance +```