Skip to content

chore: remove stray temp/comments.md from the repository root - #437

Open
martyy-code wants to merge 1 commit into
stagingfrom
chore/remove-temp-comments-md
Open

martyy-code wants to merge 1 commit into
stagingfrom
chore/remove-temp-comments-md

Conversation

@martyy-code

Copy link
Copy Markdown
Contributor

Summary

Removes the file temp/comments.md from 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/main and origin/staging. This PR targets staging; the backmerge.yml workflow will propagate the deletion to main once the PR is merged.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring
  • Test update

This is a housekeeping / chore deletion — none of the listed categories strictly apply. No author-facing behaviour changes.

Changeset

  • I have added a changeset file under .changeset/ describing this change (use pnpm changeset).
  • This PR does not affect any published package (CI, docs, internal refactor only).

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 the Version Packages flow consistent with the prior housekeeping PRs.

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas (not applicable — single-file deletion)
  • I have made corresponding changes to the documentation (not applicable — nothing to document)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works (not applicable — no behaviour change)
  • New and existing unit tests pass locally with my changes (no test surface affected)
  • Any dependent changes have been merged and published (no dependencies)

Related Issues

Screenshots (if applicable)

Additional Notes

  • The file is reachable only from origin/main, origin/staging, and the local HEAD; no feature/fix/ci branch references it. git diff origin/main..origin/staging is empty, so both branches carry the same blob.
  • Verified via git ls-tree origin/main temp and git ls-tree origin/staging temp that the file exists on both.
  • This PR deliberately does not rewrite history with git filter-repo: that would invalidate every clone/fork and break the published v1.0.0 tag.
  • @nesalia-inc/engineering is auto-assigned via .github/CODEOWNERS.

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.
@github-actions

Copy link
Copy Markdown
Contributor

Coverage report

File % Stmts % Branch % Funcs % Lines
Total 100.00% 100.00% 100.00% 100.00%
packages/fp/src/function/compose.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/const-thunks.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/constant.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/endomorphism.ts 0.00% n/a 0.00% 0.00%
packages/fp/src/function/flip.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/flow.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/function-n.ts 0.00% n/a 0.00% 0.00%
packages/fp/src/function/identity.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/index.ts 0.00% n/a 0.00% 0.00%
packages/fp/src/function/lazy.ts 0.00% n/a 0.00% 0.00%
packages/fp/src/function/pipe.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/predicate.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/function/tuple.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/tupled.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/function/untupled.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/maybe/constants.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/maybe/functions.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/maybe/index.ts 0.00% n/a 0.00% 0.00%
packages/fp/src/maybe/internal/none-impl.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/maybe/internal/some-impl.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/result/constants.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/result/functions.ts 100.00% n/a 100.00% 100.00%
packages/fp/src/result/index.ts 0.00% n/a 0.00% 0.00%
packages/fp/src/result/internal/err-impl.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/result/internal/ok-impl.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/unit/constants.ts 100.00% 100.00% 100.00% 100.00%
packages/fp/src/unit/index.ts 0.00% n/a 0.00% 0.00%

Per-file thresholds: 100% on statements / branches / functions / lines (ADR 0002). Files with no branches render n/a in the Branch column. The threshold gate is disabled in this PR and lands with the full method × variant test matrix in a follow-up.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant