Skip to content

Teach explicit ATL contexts and multi-site login - #116

Merged
Hinne1 merged 4 commits into
mainfrom
claude/atl-explicit-context-docs
Aug 27, 2026
Merged

Teach explicit ATL contexts and multi-site login#116
Hinne1 merged 4 commits into
mainfrom
claude/atl-explicit-context-docs

Conversation

@Hinne1

@Hinne1 Hinne1 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • teach every generated Jira, Confluence, and Assets example to use atl --context <alias-or-hostname>
  • support explicit multi-host authentication in the ATL installer used by environment-setup
  • document OAuth-backed Assets commands and the need to refresh tokens after CMDB scope changes
  • bump the package to 1.13.0
  • refresh the lockfile's vulnerable brace-expansion transitive dependency

Verification

  • npm run lint
  • npm run check-format
  • npm audit (0 vulnerabilities)

Dependency and release

Depends on atl-cli #74 and its v1.13.0 release.

After merge, create GitHub release v1.13.0; the release-triggered workflow publishes @enthus-appdev/llm-cli-setup@1.13.0 to GitHub Packages.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the Atlassian CLI (atl) installer and its LLM documentation to support multi-environment context handling. It modifies lib/installers/atl.js to support authenticating and checking status for multiple hosts (loginHosts) using execFileSync with the --hostname flag. It also updates the LLM system prompt in lib/llm/index.js to enforce the use of --context <alias-or-hostname> for all Jira, Confluence, and Assets operations, updating all example commands accordingly. Additionally, the package version is bumped to 1.13.0. No review comments were provided, so there is no feedback to address.

@hinne-enthus-bot

Copy link
Copy Markdown

/gemini review

@hinne-enthus-bot

Copy link
Copy Markdown

/gemini review

@hinne-enthus-bot

Copy link
Copy Markdown

🔏 Readiness attested — the pr-readiness-check gate completed for PR #116 at 12dd271dd384ad6438aa4608d273703b21068f5b (2026-08-27T13:32:27Z). If the branch head has moved, this evidence covers the earlier state only.

Readiness summary

PR Readiness Check (#116, 12dd271)
Branch/base PASS — claude/atl-explicit-context-docs -> main; mergeable and synchronized
Local verification PASS — 6 Node tests, ESLint, Prettier check, and npm audit (0 vulnerabilities)
Remote CI DEFERRED UNTIL READY — current-head NPM and CodeQL passed; license workflow is draft-gated
Coverage NOT REPORTED — repository has no coverage check
Automated reviewers LIMITATION — prior Gemini review was clean; current-head bot-triggered review produced no Gemini response
Review threads PASS — zero unresolved threads
Council findings DISPOSITIONED — multi-host login defects fixed; version/caller/re-auth claims refuted with dependency and cross-repo evidence; diagnostic/testability notes advisory
PR description PASS — behavior, tests, dependency on atl-cli v1.13.0, and merge order documented
SQL/UI evidence SKIP — installer/documentation change; no SQL or browser UI
Result: READY

@Hinne1
Hinne1 marked this pull request as ready for review August 27, 2026 13:33
@Hinne1
Hinne1 merged commit b52e59d into main Aug 27, 2026
7 checks passed
@Hinne1
Hinne1 deleted the claude/atl-explicit-context-docs branch August 27, 2026 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant