chore: remove stray temp/comments.md from the repository root - #437
Open
martyy-code wants to merge 1 commit into
Open
martyy-code wants to merge 1 commit into
martyy-code wants to merge 1 commit into
Conversation
The file was a personal brainstorming note that landed with the rewritten first commit and never belonged in the tracked tree. It is not referenced by any source, test, lint, build, or workflow.
Contributor
Coverage report
Per-file thresholds: 100% on statements / branches / functions / lines (ADR 0002). Files with no branches render |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the file
temp/comments.mdfrom the tracked tree. It is a 383-byte personal brainstorming note (turborepo, fumadocs, CI, semver, branching model) that landed with the rewritten first commit (193aa42) and was never cleaned up. It is not referenced by any source, test, lint, build, or workflow, and it ships in every clone and tarball.The file is present on both
origin/mainandorigin/staging. This PR targetsstaging; thebackmerge.ymlworkflow will propagate the deletion tomainonce the PR is merged.Type of Change
This is a housekeeping / chore deletion — none of the listed categories strictly apply. No author-facing behaviour changes.
Changeset
.changeset/describing this change (usepnpm changeset).A patch-level changeset is included at
.changeset/remove-temp-comments.md. The change has no user impact on@deessejs/fp; the patch bump keeps theVersion Packagesflow consistent with the prior housekeeping PRs.Checklist
Related Issues
Screenshots (if applicable)
Additional Notes
origin/main,origin/staging, and the local HEAD; no feature/fix/ci branch references it.git diff origin/main..origin/stagingis empty, so both branches carry the same blob.git ls-tree origin/main tempandgit ls-tree origin/staging tempthat the file exists on both.git filter-repo: that would invalidate every clone/fork and break the publishedv1.0.0tag.@nesalia-inc/engineeringis auto-assigned via.github/CODEOWNERS.