Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repo cleanup #17114

Merged
merged 1 commit into from
May 3, 2024
Merged

Repo cleanup #17114

merged 1 commit into from
May 3, 2024

Conversation

vzarytovskii
Copy link
Member

As discussed previously, removing tests we never run (i.e. they don't run in CI or part of solution), some stress tests which we haven't touched in years, moving some examples to docs.

This will allow things like Copilot/Copilot workspace not try to index those or take into account. Also, won't trigger some scanners in CI.

@vzarytovskii vzarytovskii requested a review from a team as a code owner May 2, 2024 16:17
Copy link
Contributor

github-actions bot commented May 2, 2024

✅ No release notes required

@T-Gro T-Gro merged commit 7b0dddf into dotnet:main May 3, 2024
32 checks passed
@brianrourkeboll
Copy link
Contributor

brianrourkeboll commented May 6, 2024

@vzarytovskii Did you mean to delete TheBigFileOfDebugStepping.fsx?

If so, this part of the documentation should be updated:

The file `tests\walkthroughs\DebugStepping\TheBigFileOfDebugStepping.fsx` is crucial for testing the stepping experience for a range of constructs.

If not, I can resurrect it in my PR (where I had some additions to it).

@vzarytovskii
Copy link
Member Author

I did, yeah. If it's used, we can restore it

@brianrourkeboll
Copy link
Contributor

If it's used, we can restore it

I was using it to manually verify debugging for my changes in #17067, and it did help me notice a couple bugs. It's not perfect, but it seems worth keeping around unless we have (and can document) a better alternative.

I'll restore it in that PR for now.

@vzarytovskii
Copy link
Member Author

If it's used, we can restore it

I was using it to manually verify debugging for my changes in #17067, and it did help me notice a couple bugs. It's not perfect, but it seems worth keeping around unless we have (and can document) a better alternative.

I'll restore it in that PR for now.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants