[GH-ISSUE #152] Pinned issue - GitHub Example #12

Open
opened 2026-03-04 00:40:51 +03:00 by kerem · 0 comments
Owner

Originally created by @pat-s on GitHub (Jan 19, 2025).
Original GitHub issue: https://github.com/thegeeklab/git-sv/issues/152

similar as #126

    environment:
      GITHUB_TOKEN:
        from_secret: ISSUE_TOKEN
    image: docker.io/thegeeklab/git-sv:1.0.10
    commands: |
      apk add -q --no-cache jq github-cli

      export RELEASE_NOTES=$(git sv rn)
      echo -e "RELEASE_NOTES: $RELEASE_NOTES"
      export ISSUE_NUMBER=$(gh issue list --json number --state open --search "Changelog for upcoming version" | jq -r '.[] | .number')

      if [ -z "$ISSUE_NUMBER" ]; then
        gh issue create --title "Changelog for upcoming version" --body "$RELEASE_NOTES"
      else
        gh issue edit $ISSUE_NUMBER --body "$RELEASE_NOTES"
      fi
Originally created by @pat-s on GitHub (Jan 19, 2025). Original GitHub issue: https://github.com/thegeeklab/git-sv/issues/152 similar as #126 ```yaml environment: GITHUB_TOKEN: from_secret: ISSUE_TOKEN image: docker.io/thegeeklab/git-sv:1.0.10 commands: | apk add -q --no-cache jq github-cli export RELEASE_NOTES=$(git sv rn) echo -e "RELEASE_NOTES: $RELEASE_NOTES" export ISSUE_NUMBER=$(gh issue list --json number --state open --search "Changelog for upcoming version" | jq -r '.[] | .number') if [ -z "$ISSUE_NUMBER" ]; then gh issue create --title "Changelog for upcoming version" --body "$RELEASE_NOTES" else gh issue edit $ISSUE_NUMBER --body "$RELEASE_NOTES" fi ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/git-sv#12
No description provided.