Skip to content

chore: remove the stray .agiloft-spec working notes - #6605

Merged
waleedlatif1 merged 1 commit into
stagingfrom
chore/remove-agiloft-spec
Aug 12, 2026
Merged

chore: remove the stray .agiloft-spec working notes#6605
waleedlatif1 merged 1 commit into
stagingfrom
chore/remove-agiloft-spec

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

  • .agiloft-spec/SPEC.md (233 lines of transcribed Agiloft REST docs) was committed by accident in fix(agiloft): repoint the block at the alrest surface and fix EWLogin #6562 (be5db68644), alongside the alrest repointing work
  • Nothing imports, links, or references it — git grep agiloft-spec outside the directory itself returns nothing
  • It sits in a dot-directory at the repo root rather than anywhere docs live, and the integration it informed has shipped

Not a disclosure

The repo is public, so I scanned it before removing. Every credential and host in it is the vendor's own documentation placeholder — $login=user&$password=passwd, admin/qwerty, https://server, localhost. No real tenant hostnames, tokens, or keys. Nothing sensitive was exposed while it was there.

Type of Change

  • Chore

Testing

Deletion only — no code references it, so nothing to exercise. If the notes are still wanted as reference, the right home is apps/docs, not a root dot-directory; happy to move rather than delete.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Transcribed Agiloft REST docs committed by accident in #6562 alongside the
alrest repointing. Nothing imports or links it, it sits in a dot-directory at
the repo root rather than anywhere docs live, and the integration it informed
has shipped. Contents are the vendor's own public examples — placeholder
credentials and localhost hosts only, so nothing sensitive was exposed while
it was public.
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview Aug 12, 2026 5:17am

Request Review

@cursor

cursor Bot commented Aug 12, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only deletion of an unreferenced file; no runtime, security, or behavioral impact.

Overview
Removes the accidentally committed .agiloft-spec/SPEC.md working notes (transcribed Agiloft REST docs) that were checked in with earlier alrest work.

Nothing in the repo imports or references this file, and it lived in a root dot-directory rather than docs. No sensitive credentials were present—only vendor documentation placeholders.

Reviewed by Cursor Bugbot for commit 11ebd9e. Configure here.

@waleedlatif1
waleedlatif1 merged commit a40e379 into staging Aug 12, 2026
5 of 6 checks passed
@waleedlatif1
waleedlatif1 deleted the chore/remove-agiloft-spec branch August 12, 2026 05:11
@greptile-apps

greptile-apps Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR removes an accidentally committed, unreferenced set of Agiloft REST API working notes.

  • Deletes .agiloft-spec/SPEC.md.
  • Leaves the implementation and published Agiloft documentation unchanged.

Confidence Score: 5/5

The PR appears safe to merge because the deleted notes have no identified repository consumer.

The change only removes an isolated working-notes file; tracked code, documentation, tests, and build configuration do not reference or implicitly discover it.

Important Files Changed

Filename Overview
.agiloft-spec/SPEC.md Deletes an unreferenced working-notes document with no identified build, runtime, documentation, or integration consumer.

Reviews (1): Last reviewed commit: "chore: remove the stray .agiloft-spec wo..." | Re-trigger Greptile

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