blw-ofag-ufag/atlas-code-github-workflows
Watch
2
mirror of https://github.com/blw-ofag-ufag/atlas-code-github-workflows.git synced 2026-08-26 10:04:33 +00:00
Code Releases Activity
Read-only mirror of https://github.com/blw-ofag-ufag/atlas-code-github-workflows — Bundesamt für Landwirtschaft. Issues & pull requests at the source.
20 commits 4 branches 9 tags 168 KiB
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
gh-org-app-token-read-write[bot] b3c08c351b
 chore(main): release 1.2.1 (#30) 
Co-authored-by: gh-org-app-token-read-write[bot] <243126968+gh-org-app-token-read-write[bot]@users.noreply.github.com>
2026-08-19 13:22:48 +02:00
.github fix: gate e2e semantic-release on all preceding checks (#31) 2026-08-19 13:22:10 +02:00
docs fix: owasp dependency check, image push to ECR (#20) 2026-04-21 15:47:08 +02:00
.gitattributes feat(init): adds initial gitlab workflows 2026-04-07 17:57:15 +02:00
.gitignore fix: owasp dependency check, image push to ECR (#20) 2026-04-21 15:47:08 +02:00
CHANGELOG.md chore(main): release 1.2.1 (#30) 2026-08-19 13:22:48 +02:00
README.md feat(init): adds initial gitlab workflows 2026-04-07 17:57:15 +02:00

README.md

🔄 Atlas GitHub Pipeline Workflows

📋 Overview

Generalized CI/CD workflows for use across multiple projects in the BLW ecosystem.

🌿 GitFlow Branching Strategy

The main workflows (backend_workflow.yml and frontend_workflow.yml) are designed with the GitFlow branching strategy in mind.

Semantic versioning is used to automatically update versions based on commit messages and branch names. The branching strategy is as follows:

Branch Purpose Version Behavior Deployment
develop Prerelease branch for features, updated via PRs from feature branches Updates prerelease suffix (e.g. 1.0.0-rc.x) 🚀 Deploys to dev
main Production-ready code, updated via PRs from develop or hotfix branches Bumps to next stable release (e.g. 1.0.0) 🚀 Deploys to int
feature/* New features or bug fixes, merged into develop when complete ➖ No version update 🔍 Analysis & tests only
hotfix/* Urgent fixes for production issues, merged into both main and develop ➖ No version update 🔍 Analysis & tests only

🚀 Prod Releases

There is currently no automated workflow for production releases. A pipeline that can be manually triggered to deploy a specific version to any stage is planned for the future.

📚 Documentation

Guide Description
🎨 Frontend Workflow Setup guide for Node/pnpm frontend projects
📋 Backend Workflow Setup guide for Java/Maven backend projects
🗂️ Workflows Overview Reference for all individual workflows in .github/workflows/