From 166b8c6e9f8bc26e109875c6e8bc70c218798dad Mon Sep 17 00:00:00 2001
From: mrizzi <mrizzi@redhat.com>
Date: Thu, 9 Jul 2026 12:41:02 +0200
Subject: [PATCH] fix(docs): use explicit repo name instead of hardcoded remote
 in release instructions

Assisted by: Claude Code (claude-opus-4-6-20250709)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 docs/releasing.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/releasing.md b/docs/releasing.md
index 222b22ab1..efb71ec4b 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -21,11 +21,11 @@ This document describes how to release a new version of the sdlc-workflow plugin
 
 4. **Push to the default branch.**
 
-5. **Create a GitHub release** — tag the release commit and create a GitHub release with notes from the changelog:
+5. **Create a GitHub release** — tag the release commit and create a GitHub release on `RHEcosystemAppEng/sdlc-plugins` with notes from the changelog:
    ```bash
    git tag vX.Y.Z <commit-sha>
-   git push origin vX.Y.Z
-   gh release create vX.Y.Z --title "vX.Y.Z" --latest --notes "<changelog section for this version>"
+   git push <remote> vX.Y.Z   # push to RHEcosystemAppEng/sdlc-plugins
+   gh release create vX.Y.Z --repo RHEcosystemAppEng/sdlc-plugins --title "vX.Y.Z" --latest --notes "<changelog section for this version>"
    ```
    Use the corresponding `CHANGELOG.md` section as the release notes body.