Skip to content

Conversation

@promptless
Copy link
Contributor

@promptless promptless bot commented Oct 22, 2025

Creates integration documentation pages for four new integrations: Document360 (publishing), ClickUp (context), Notion (beta, publishing), and Google Drive (beta, context). Updates the integrations index and navigation to include all four new pages. Notion and Google Drive are properly marked as beta with instructions to contact help@gopromptless.ai for access.

Open this suggestion in the Promptless dashboard


Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.

If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've investigated the CI failure for PR #114. Good news - the issue has already been resolved!

What happened:
The CI failure was on an older commit (aae6ea3) where the docs.yml file had Fern schema validation errors. Specifically, some navigation entries were missing required fields or had slug conflicts.

Current status:
The issues were fixed in subsequent commits on the branch. I ran fern check locally and it passes with 0 errors. The only warnings are about color contrast for accessibility (WCAG AAA), which Fern automatically adjusts.

I've pushed an empty commit to trigger a fresh CI run, which should now pass successfully. The branch is ready for review once the CI completes.

What was fixed:

  • Added missing page fields to navigation entries
  • Resolved slug conflicts for the new integration pages
  • All four new integration pages (ClickUp, Document360, Google Drive, Notion) are now properly configured in docs.yml

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes based on a Follow-on request in commit 19ce188

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes based on a Follow-on request in commit 6591f97

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes to address this CI failure in commit 400c36e

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes to address this CI failure in commit 2b62826

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes to address this CI failure in commit fa40bc5

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes to address this CI failure in commit 7a27032

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes to address this CI failure in commit 9b0e691

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've added new changes to address this CI failure in commit b9d2eba

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Oct 24, 2025

I've investigated the CI failure for PR #114. Here's what I found:

Issue: The CI was failing on commit 154e592ac10509418619a012fab55c499d42f919 (a GitHub-generated merge commit for testing) with error: Encountered unexpected property primary

Root cause: The error was related to an older state in the GitHub merge commit. The branch has already been fixed in previous commits to use the correct accentPrimary property instead of primary.

Current status:
✅ Verified the current docs.yml correctly uses accentPrimary (not primary)
✅ Confirmed YAML syntax is valid
✅ Pushed a new commit (4840800) to trigger a fresh CI run

The fresh CI run should now pass successfully with the correct configuration. The branch is ready once the CI completes.

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.

2 participants