Skip to content

Fix IDEA setup to skip .claude directory and add scripts module#63607

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:fix-idea-setup-exclude-claude-add-scripts
Mar 14, 2026
Merged

Fix IDEA setup to skip .claude directory and add scripts module#63607
potiuk merged 1 commit intoapache:mainfrom
potiuk:fix-idea-setup-exclude-claude-add-scripts

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Mar 14, 2026

Fix IDEA setup script to exclude .claude directory from pyproject.toml discovery
and IML cleanup scans, and add scripts distribution to the static modules list.

  • Add .claude/ to EXCLUDED_PREFIXES — prevents rglob from picking up
    pyproject.toml files inside .claude/worktrees/
  • Add .claude to _CLEANUP_SKIP_DIRS — prevents the IML cleanup scan from
    entering .claude/
  • Add scripts to STATIC_MODULES — includes the scripts distribution

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6) following the guidelines

- Add `.claude/` to EXCLUDED_PREFIXES so pyproject.toml discovery
  skips `.claude/worktrees/` directories
- Add `.claude` to _CLEANUP_SKIP_DIRS so IML cleanup ignores it
- Add `scripts` to STATIC_MODULES for the scripts distribution
@potiuk potiuk merged commit 0e11c84 into apache:main Mar 14, 2026
107 of 108 checks passed
@potiuk potiuk deleted the fix-idea-setup-exclude-claude-add-scripts branch March 14, 2026 17:26
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 0e11c84 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

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

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants