Conversation
🤖 My Senior Dev — Analysis Complete👤 For @khaliqgant📁 Expert in View your contributor analytics → 📊 17 files reviewed • 4 need attention 🚨 High Risk:
📚 Relevant Past Discussions:
🚀 Open Interactive Review →The full interface unlocks features not available in GitHub:
💬 Chat here: 📖 View all 12 personas & slash commandsYou can interact with me by mentioning In PR comments or on any line of code:
Slash commands:
AI Personas (mention to get their perspective):
For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews. |
| </Step> | ||
| <Step title="Configure the redirect URL"> | ||
| On the created app page, select the _Build_ dropdown at the right side of the page. | ||
| Select _OAuth and Permissions_ |
There was a problem hiding this comment.
[Documentation] Add a period at the end of "Select OAuth and Permissions" to keep sentence punctuation consistent in this step.
Context for Agents
[**Documentation**]
Add a period at the end of "Select _OAuth and Permissions_" to keep sentence punctuation consistent in this step.
File: docs/api-integrations/monday/how-to-register-your-own-monday-api-oauth-app.mdx
Line: 25|
|
||
| ## Important API Considerations | ||
|
|
||
| **Refresh token expiration:** Refresh tokens will expire after 365 days of non-use and will expire by 90 days if the resource owner is inactive for 90 days. Make sure you call `nango.getConnection()` at least every 365 days to trigger a refresh. See [Atlassian's OAuth documentation](https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/#how-do-i-get-a-new-access-token--if-my-access-token-expires-or-is-revoked-) for more details. |
There was a problem hiding this comment.
[Documentation] Fix grammar: change "will expire by 90 days" to "will expire after 90 days" (or similar) to accurately describe the 90-day inactivity expiration.
Context for Agents
[**Documentation**]
Fix grammar: change "will expire by 90 days" to "will expire after 90 days" (or similar) to accurately describe the 90-day inactivity expiration.
File: docs/api-integrations/atlassian/how-to-register-your-own-atlassian-api-oauth-app.mdx
Line: 58| <img src="/integrations/all/workday/credentials.png" /> | ||
| 4. Confirm the ISU account has been created by viewing **All Workday Accounts** and filter on the **Username** you created. | ||
| <img src="/integrations/all/workday/confirm_user.png" /> | ||
| 5.Go to the search bar and type **Create Security Group** then select it. |
There was a problem hiding this comment.
[Documentation] Insert a space after "5." so the ordered list renders correctly.
Context for Agents
[**Documentation**]
Insert a space after "5." so the ordered list renders correctly.
File: docs/api-integrations/workday/connect.mdx
Line: 41| <img src="/integrations/all/workday/view_isu_group.png" /> | ||
| 12. Add all of the required domain security policies with the proper view/modify access for the **Integration Permissions**. | ||
| <Tip>In Workday, all security changes remain **pending** until they are activated by a user with the appropriate permissions.</Tip> | ||
| 13. Activate your security policy changes by; |
There was a problem hiding this comment.
[Documentation] Replace the semicolon after "Activate your security policy changes by" with a colon to introduce the following list properly.
Context for Agents
[**Documentation**]
Replace the semicolon after "Activate your security policy changes by" with a colon to introduce the following list properly.
File: docs/api-integrations/workday/connect.mdx
Line: 57|
This PR is stale because it has been open for 30 days with no activity. |
| 11. Navigate to **ellipses** > **Security Group** > **Maintain Domain Permissions for Security Group**. | ||
| <img src="/integrations/all/workday/view_isu_group.png" /> | ||
| 12. Add all of the required domain security policies with the proper view/modify access for the **Integration Permissions**. | ||
| <Tip>In Workday, all security changes remain **pending** until they are activated by a user with the appropriate permissions.</Tip> |
There was a problem hiding this comment.
[Documentation] Replace the typo by; with by: and indent the three hyphenated steps beneath it so they stay nested under Step 13 rather than starting a new top-level list.
Context for Agents
[**Documentation**]
Replace the typo `by;` with `by:` and indent the three hyphenated steps beneath it so they stay nested under Step 13 rather than starting a new top-level list.
File: docs/api-integrations/workday/connect.mdx
Line: 56
Builds on #5056 and #5037
Migrates over
Docs migration for seven integrations with updated navigation & provider metadata
This PR migrates the Atlassian, Greenhouse, ServiceNow, Workday, Monday, DocuSign, and Lever integration docs into the new IA structure, adding quickstart guides, setup instructions, and SCIM/connect specifics. It also aligns site navigation, redirects, and
providers.yamlmetadata to the new/api-integrations/...slug structure so in-product links resolve to the restructured pages.Key Changes
• Added new
docs/api-integrations/*guides (quickstart, setup, connect) for Atlassian, Greenhouse, ServiceNow, Workday, Monday, DocuSign, and Lever with updated frontmatter and embedded examples.• Updated
docs/docs.jsonnavigation, sidebar entries, and redirects to point legacy/integrations/all/...slugs to the new/api-integrations/...locations.• Refreshed
packages/providers/providers.yamlfor the affected providers sodocs,setup_guide_url, anddocs_connectfields reference the new documentation paths.Affected Areas
• Documentation site content under
docs/api-integrations• Navigation/redirect configuration in
docs/docs.json• Provider metadata in
packages/providers/providers.yamlThis summary was automatically generated by @propel-code-bot