docs: update license to JumpCloud Community Software Tool#11
Merged
Conversation
Update copyright holder to JumpCloud and add community software tool disclaimer clarifying that JumpCloud does not commit to maintaining or supporting this project. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Replace all GitHub URLs across README, QUICKSTART, and blog post - Fix clone instructions (cd jc → cd jc-cli) - Update license disclaimer in blog post Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jrennichjc
approved these changes
Apr 14, 2026
jklaassenjc
pushed a commit
that referenced
this pull request
Jun 5, 2026
…tion (Bugbot KLA-439) Tenth and eleventh Bugbot findings on PR #42 (both Medium). **#10: --org flag source ignored.** root.go's PersistentPreRunE calls config.OverrideActiveProfile when --org is set, but collectProfile only knew about JC_PROFILE env / config / "default". An operator running `jc doctor --org staging` saw the right ActiveProfile but the source said "config (or default)" — the report lied about how the profile was selected. Fix: collectProfile takes a flagOrgSet bool; plumb the root command's --org .Changed bit through (same pattern as flagAPIKeySet for the api-key flag). **#11: probe-timeout vs parent-context attribution.** When the parent context's deadline fires first (global --timeout, signal cancel), my ctx.Done() branch always blamed --probe-timeout. Fix: peek at parentCtx.Err() in the timeout branch — if non-nil, the parent fired first, so the error message points at the global --timeout instead. After these two, every field doctor reports has a precedence attribution that matches what jc actually used. Same surgical class as finding #9 — bounded, no compounding cases possible because the field enumerations are exhausted. Tests: - TestCollectProfile_OrgFlagOverridesAll - TestRunAPIProbe_ParentContextDeadlineBlamedCorrectly 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
3 participants
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.
Summary
juergen-kc/jc→TheJumpCloud/jc-cliacross README, QUICKSTART, and blog postcd jc→cd jc-cli)🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changes update licensing attribution and repository/issue URLs, with no code or runtime behavior impact.
Overview
Updates legal and project messaging to reflect JumpCloud ownership and Community Software Tool positioning.
Changes the
LICENSEcopyright holder to JumpCloud, updatesREADME.mdlicense section with a JumpCloud disclaimer and new issue tracker link, and rewrites install/clone URLs acrossREADME.md,docs/QUICKSTART.md, and the intro blog post to point toTheJumpCloud/jc-cli.Reviewed by Cursor Bugbot for commit 8868327. Bugbot is set up for automated code reviews on this repo. Configure here.