- descriptions state WHEN each skill applies - jira-workflow ships curl scripts reading TRACKER_URL/JIRA_TOKEN from env, no hardcoded secrets/URLs - repo-map/docs-map defer values to session corporate context; company specifics left as TODO - go-standards uses realistic Go defaults, company-specific bits marked TODO
23 lines
1001 B
Bash
Executable File
23 lines
1001 B
Bash
Executable File
#!/usr/bin/env bash
|
||
# link-mr.sh <ISSUE_KEY> "<mr-url>" ["<title>"]
|
||
# Attaches a merge request link to a tracker issue.
|
||
# Default implementation posts a comment with the link (works on any Jira).
|
||
# Reads TRACKER_URL and JIRA_TOKEN from the environment. No secrets are hardcoded.
|
||
set -euo pipefail
|
||
|
||
KEY="${1:?usage: link-mr.sh <ISSUE_KEY> \"<mr-url>\" [\"<title>\"]}"
|
||
URL="${2:?usage: link-mr.sh <ISSUE_KEY> \"<mr-url>\" [\"<title>\"]}"
|
||
TITLE="${3:-Merge request}"
|
||
: "${TRACKER_URL:?set TRACKER_URL (or take the tracker address from the session corporate context)}"
|
||
: "${JIRA_TOKEN:?set JIRA_TOKEN (tracker personal access token)}"
|
||
|
||
BASE="${TRACKER_URL%/}"
|
||
|
||
# Default: comment with the MR link.
|
||
COMMENT="${TITLE}: ${URL}"
|
||
exec "$(dirname "$0")/add-comment.sh" "$KEY" "$COMMENT"
|
||
|
||
# TODO: если в компании используется remote issue link API, заменить на:
|
||
# POST ${BASE}/rest/api/2/issue/${KEY}/remotelink
|
||
# с телом {"object":{"url":"<URL>","title":"<TITLE>"}}
|