Skip to content

Comments

[DOCS] Add Windows long-path guidance for contributors#11632

Open
schen9999 wants to merge 3 commits intogreat-expectations:developfrom
schen9999:fix/windows-long-paths-doc
Open

[DOCS] Add Windows long-path guidance for contributors#11632
schen9999 wants to merge 3 commits intogreat-expectations:developfrom
schen9999:fix/windows-long-paths-doc

Conversation

@schen9999
Copy link

Summary

Adds a short Windows-specific note to the contributor documentation explaining how to avoid Filename too long errors when cloning the repository.

Motivation

Cloning the repository on Windows can fail due to deep documentation paths and default OS path length limits. This change documents the required configuration to prevent setup failures for new contributors.

Changes

  • Added Windows long-path setup instructions to contributor resources.

Validation

  • Verified the issue locally on Windows
  • Confirmed guidance resolves the clone failure

Checklist

  • Documentation updated
  • No code changes required

@netlify
Copy link

netlify bot commented Feb 4, 2026

‼️ Deploy request for niobium-lead-7998 rejected.

Name Link
🔨 Latest commit 6c2b191

@gx-cla-bot
Copy link

gx-cla-bot bot commented Feb 4, 2026

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: samuel.chen@utdallas.edu

@schen9999
Copy link
Author

@cla-bot check

@gx-cla-bot
Copy link

gx-cla-bot bot commented Feb 4, 2026

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: samuel.chen@utdallas.edu

Copy link
Contributor

@wookasz wookasz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the contribution!

@gx-cla-bot
Copy link

gx-cla-bot bot commented Feb 4, 2026

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: samuel.chen@utdallas.edu

@codecov
Copy link

codecov bot commented Feb 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.16%. Comparing base (eac594e) to head (6c2b191).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #11632      +/-   ##
===========================================
- Coverage    84.18%   84.16%   -0.02%     
===========================================
  Files          471      471              
  Lines        39592    39592              
===========================================
- Hits         33330    33324       -6     
- Misses        6262     6268       +6     
Flag Coverage Δ
3.10 ?
3.10 athena 41.50% <ø> (ø)
3.10 aws_deps 45.86% <ø> (ø)
3.10 big 55.19% <ø> (ø)
3.10 bigquery 50.67% <ø> (ø)
3.10 clickhouse 41.51% <ø> (ø)
3.10 databricks 52.43% <ø> (ø)
3.10 filesystem 63.95% <ø> (ø)
3.10 gx-redshift 50.67% <ø> (ø)
3.10 mssql 50.79% <ø> (ø)
3.10 mysql 51.07% <ø> (ø)
3.10 openpyxl or pyarrow or project or sqlite or aws_creds 59.24% <ø> (ø)
3.10 postgresql 54.71% <ø> (ø)
3.10 snowflake 53.24% <ø> (-0.01%) ⬇️
3.10 spark 55.34% <ø> (+<0.01%) ⬆️
3.10 spark_connect 46.36% <ø> (ø)
3.10 trino 48.17% <ø> (ø)
3.11 72.66% <ø> (-0.02%) ⬇️
3.11 athena ?
3.11 aws_deps ?
3.11 big ?
3.11 clickhouse ?
3.11 mssql ?
3.11 mysql ?
3.11 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.11 spark_connect ?
3.12 ?
3.12 athena ?
3.12 aws_deps ?
3.12 big ?
3.12 mssql ?
3.12 mysql ?
3.12 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.12 spark_connect ?
3.13 ?
3.13 athena 41.50% <ø> (ø)
3.13 aws_deps 45.86% <ø> (ø)
3.13 big 55.18% <ø> (ø)
3.13 bigquery 50.67% <ø> (ø)
3.13 clickhouse 41.51% <ø> (ø)
3.13 databricks 52.43% <ø> (ø)
3.13 filesystem 63.95% <ø> (ø)
3.13 gx-redshift 50.67% <ø> (ø)
3.13 mssql 50.79% <ø> (ø)
3.13 mysql 51.07% <ø> (ø)
3.13 openpyxl or pyarrow or project or sqlite or aws_creds 59.24% <ø> (ø)
3.13 postgresql 54.71% <ø> (ø)
3.13 snowflake 53.25% <ø> (ø)
3.13 spark 55.34% <ø> (ø)
3.13 spark_connect 46.37% <ø> (ø)
3.13 trino 48.18% <ø> (ø)
cloud 0.00% <ø> (ø)
docs-basic 58.51% <ø> (ø)
docs-creds-needed 57.31% <ø> (ø)
docs-spark 56.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@wookasz
Copy link
Contributor

wookasz commented Feb 4, 2026

@cla-bot check

@gx-cla-bot
Copy link

gx-cla-bot bot commented Feb 4, 2026

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: samuel.chen@utdallas.edu

@gx-cla-bot
Copy link

gx-cla-bot bot commented Feb 4, 2026

A new contributor, HUZZAH! Welcome and thanks for joining our community. In order to accept a pull request we require that all contributors sign our Contributor License Agreement. We have two different CLAs, depending on whether you are contributing to GX in a personal or professional capacity. Please sign the one that is applicable to your situation so that we may accept your contribution:

Individual Contributor License Agreement v1.0
Software Grant and Corporate Contributor License Agreement v1.0

Once you have signed the CLA, you can add a comment with the text @cla-bot check and the bot will update the PR status!

Please reach out to the #gx-community-support channel, on our Slack if you have any questions or if you have already signed the CLA and are receiving this message in error.

Users missing a CLA: samuel.chen@utdallas.edu

@wookasz
Copy link
Contributor

wookasz commented Feb 4, 2026

@schen9999 looks like your signed CLA is missing. Please make sure to fill out one of the two agreements ensuring the email address matches the one for your GitHub account.

If you're having issues with the doc, please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants