Repository navigation
[docs-patrol] Update JumpCloud README to document newly visible starting_point option #19025
Description
Recent code changes in the repository have introduced documentation drift. The following change needs a corresponding documentation update.
Changes Requiring Documentation Updates
1. JumpCloud starting_point is now user-visible but not documented in package README
Commit(s): d43ff234d21161ef4cbbc25d56415e4aa72680d9
What changed: In packages/jumpcloud/data_stream/events/manifest.yml, starting_point was changed from hidden advanced config to visible user config (show_user: true) and gained explicit format guidance (Go duration syntax, unsupported d unit, examples) with default -360h.
Documentation impact: packages/jumpcloud/docs/README.md should include this setting in the configuration section (purpose, accepted format, examples, and default) so users configuring the integration understand how to set it correctly.
Evidence:
- New visible option and guidance:
packages/jumpcloud/data_stream/events/manifest.ymllines 30-40 - README configuration section omits
starting_point:packages/jumpcloud/docs/README.mdlines 23-39 (and nostarting_pointmention in file)
Suggested Actions
- Add a "Starting point" subsection to
packages/jumpcloud/docs/README.mdunder Configuration. - Document accepted value format (negative Go duration with
h/m/s), unsupporteddunit, and examples from manifest. - Document the default value (
-360h) and clarify first-run behavior.
Note
🔒 Integrity filter blocked 22 items
The following items were blocked because they don't meet the GitHub integrity level.
- #18991
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18980
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18889
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18552
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18802
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18516
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18141
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18227
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18345
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18762
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18777
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18965
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #17506
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18931
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18930
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #18700
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - ... and 6 more items
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools:
github:
min-integrity: approved # merged | approved | unapproved | noneWhat is this? | From workflow: Docs Patrol
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
- expires on May 22, 2026, 10:54 AM UTC
Activity