docs: add enterprise directory PR restriction notice#453
Conversation
Co-authored-by: openhands <openhands@all-hands.dev>
|
@OpenHands the mintlify preview seems broken. Can you investigate why? |
|
I'm on it! jpelletier1 can track my progress at all-hands.dev |
|
I investigated the Mintlify preview and found that the preview is actually working correctly for the changed file. What I found:
About the 404 pages: Verification:
To verify the full site locally, you can run: npx mintlify devThe PR changes are ready for review. Is there anything specific about the preview that looked broken to you? |
Final SummaryI investigated the Mintlify preview issue for PR #453 as requested. Investigation ResultsThe preview is NOT broken - it's working as expected for Mintlify PR previews. Findings:
Root Cause of 404s: Action TakenI posted a comment on PR #453 explaining the investigation results and asking if there was something specific that looked broken to the user. No Code Changes MadeThis was purely an investigation task - no code modifications were needed because the PR changes are correct and functioning as intended. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Co-authored-by: openhands <openhands@all-hands.dev>
Update: Found the root causeI've identified this is a known Mintlify bug: Preview deployments show 404s if branch name was used in prior deployments. The issue:When a branch name (like Symptoms we're seeing:
Workaround:A manual redeployment from the Mintlify Dashboard should fix this. Someone with access to the Mintlify dashboard can:
Note:This is a Mintlify-side issue, not a problem with the PR changes. The documentation changes are correct - you can verify by running |
|
Mintlify preview now working. Here's a preview of the change: https://allhandsai-docs-enterprise-pr-restriction.mintlify.app/overview/contributing#pull-request-process |
all-hands-bot
left a comment
There was a problem hiding this comment.
🟢 Good taste - Clear documentation of contribution boundaries. Solves a real problem (users need to know where they can contribute) with straightforward language. One minor suggestion below about temporal weasel words.
Summary of changes
Adds a warning notice under the "Pull Request Process" section of the contributing page explaining that:
enterprise/directory of the OpenHands/OpenHands repository cannot be accepted at this time, as this part of the codebase is commercially licensedThe warning includes links to:
This PR was created by an AI assistant (OpenHands) on behalf of the user.
@jpelletier1 can click here to continue refining the PR