Skip to content

chore: remove Go/binary template artifacts irrelevant to TypeScript SDK#7

Open
Atharva0506 wants to merge 1 commit into
AOSSIE-Org:mainfrom
Atharva0506:chore/remove-go-template-artifacts
Open

chore: remove Go/binary template artifacts irrelevant to TypeScript SDK#7
Atharva0506 wants to merge 1 commit into
AOSSIE-Org:mainfrom
Atharva0506:chore/remove-go-template-artifacts

Conversation

@Atharva0506

@Atharva0506 Atharva0506 commented Jul 13, 2026

Copy link
Copy Markdown
Member

Addressed Issues:

Fixes #(issue number)
This is a TypeScript npm package. Several files were auto-added by the AOSSIE org Go template and are irrelevant.

Screenshots/Recordings:

Additional Notes:

Removed:

  • .goreleaser.yaml — Go binary release tool config
  • .github/workflows/release-goreleaser.yml — GoReleaser CI workflow
  • .github/workflows/osv-scanner-pr.yml — Go vulnerability scanner
  • .github/workflows/osv-scanner-release.yml — Go vulnerability scanner
  • .github/workflows/osv-scanner-scheduled.yml — Go vulnerability scanner
  • .github/workflows/gitleaks-scanning.yml — Secrets scanner
    npm-specific security scanning is already handled by the existing dependency-review-action.yml and codeql.yml workflows.

Checklist

  • My code follows the project's code style and conventions
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings or errors
  • I have joined the Discord server and I will share a link to this PR with the project maintainers there
  • I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

Summary by CodeRabbit

  • Chores
    • Removed automated secret scanning and dependency vulnerability scanning workflows.
    • Removed scheduled, pull request, and release security checks.
    • Removed the automated GoReleaser release workflow and its packaging configuration.
    • Automated builds, security scans, and artifact publishing are no longer configured through the repository’s workflows.

This is a TypeScript npm package — the following files were auto-added
by the AOSSIE org template but are irrelevant for this project:

Removed:
- .goreleaser.yaml (Go binary release tool)
- .github/workflows/release-goreleaser.yml (GoReleaser CI)
- .github/workflows/osv-scanner-pr.yml (Go vulnerability scanner)
- .github/workflows/osv-scanner-release.yml (Go vulnerability scanner)
- .github/workflows/osv-scanner-scheduled.yml (Go vulnerability scanner)
- .github/workflows/gitleaks-scanning.yml (secrets scanner)

Note: npm-specific security scanning is handled by the existing
dependency-review-action.yml and CodeQL workflows.
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 458e5445-3762-49d2-ab72-bbb9dadae1e6

📥 Commits

Reviewing files that changed from the base of the PR and between b88e93d and cd378db.

📒 Files selected for processing (6)
  • .github/workflows/gitleaks-scanning.yml
  • .github/workflows/osv-scanner-pr.yml
  • .github/workflows/osv-scanner-release.yml
  • .github/workflows/osv-scanner-scheduled.yml
  • .github/workflows/release-goreleaser.yml
  • .goreleaser.yaml
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • AOSSIE-Org/ThruBox-Server (manual)
💤 Files with no reviewable changes (6)
  • .github/workflows/osv-scanner-pr.yml
  • .github/workflows/release-goreleaser.yml
  • .github/workflows/gitleaks-scanning.yml
  • .github/workflows/osv-scanner-release.yml
  • .github/workflows/osv-scanner-scheduled.yml
  • .goreleaser.yaml

Walkthrough

Removed GitHub Actions workflows for secret scanning, OSV scanning, and GoReleaser releases, along with the GoReleaser configuration.

Changes

Cohort / File(s) Summary
Security scanning workflows
.github/workflows/gitleaks-scanning.yml, .github/workflows/osv-scanner-*.yml
Removed Gitleaks and OSV-Scanner pull request, release, scheduled, and push workflows.
Release configuration
.github/workflows/release-goreleaser.yml, .goreleaser.yaml
Removed the GoReleaser release workflow and its packaging, checksum, SBOM, and archive configuration.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

A rabbit hops where workflows ran,
No scans or releases in the plan.
The config leaves, the pipelines sleep,
While carrots safely pile in a heap.

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: removing Go/binary template artifacts from the TypeScript SDK repo.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added no-issue-linked PR is not linked to any issue backend Changes to backend code ci-cd CI/CD pipeline changes configuration Configuration file changes github-actions GitHub Actions workflow changes size/L Large PR (201-500 lines changed) repeat-contributor PR from an external contributor who already had PRs merged needs-review labels Jul 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor
Messages
📖

⚠️ PR Template Check

These are non-blocking, but please fix:

  • Please replace the placeholder Fixes #(issue number) with the actual issue number (e.g. Fixes #42).

  • Some required checklist items are not completed:

  • My PR addresses a single issue

Generated by 🚫 dangerJS against cd378db

@Atharva0506
Atharva0506 marked this pull request as ready for review July 13, 2026 14:31
@Atharva0506

Copy link
Copy Markdown
Member Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

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

Labels

backend Changes to backend code ci-cd CI/CD pipeline changes configuration Configuration file changes github-actions GitHub Actions workflow changes needs-review no-issue-linked PR is not linked to any issue repeat-contributor PR from an external contributor who already had PRs merged size/L Large PR (201-500 lines changed)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant