ci: unify on github-workflow-standard#15
Merged
Conversation
- maven.yml → build.yml: build-only, push (branches-ignore main) + PR, concurrency, least-priv permissions; JDK-Matrix [11,17,21] behalten; mvn verify statt compile test. - Toten ACCESS_TOKEN-Env-Var entfernt (in keiner pom.xml referenziert). - release.yml: explizite permissions: contents: write (JitPack/README, push→GitHub-Release). - Runner unverändert ubuntu-latest (kein self-hosted). Standard: personal vault/concepts/github-workflow-standard.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fae4b74 to
570fc3a
Compare
This was referenced May 26, 2026
Reviewer via CODEOWNERS, Assignee via auto-assign workflow. Standard: personal vault/concepts/github-workflow-standard.md Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vereinheitlicht die CI auf den github-workflow-standard (
personalvaultconcepts/github-workflow-standard.md). Muster-PR für die ZrdJ-Org.Änderungen
maven.yml→build.yml: build-only, nurpush(alle Branches außermain, keinpull_request→ keine Doppel-Läufe; PR erbt die 3 Checks via Head-SHA).concurrency, least-privpermissions: contents: read, JDK-Matrix[11,17,21]behalten,mvn -B -ntp verify.checkout@v4,setup-java@v4).ACCESS_TOKEN-Env entfernt — in keinerpom.xmlreferenziert (dependency-freie Lib). Macht das ZrdJ-Org-SecretACCESS_TOKENunbenutzt.release.yml: explizitepermissions: contents: write(JitPack-Trigger + README-Bump unverändert)..github/CODEOWNERS(* @codejanovic) → Auto-Review-Request..github/workflows/auto-assign.yml→ setztcodejanovicals Assignee.Checkliste (github-workflow-standard)
ACCESS_TOKENjetzt unbenutzt → ZrdJ-Org-Secret entfernbarubuntu-latest✅mainein required status checkJava CI with Mavenexistiert, auf den neuen Kontext (Build for JDK …) umstellen.🤖 Generated with Claude Code