Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #5160] [MERGED] chore: add ESLint CI workflow #5329

New Issue
Closed
opened 2026-06-05 15:21:00 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 15:21:00 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/5160
Author: @angelplusultra
Created: 3/6/2026
Status: ✅ Merged
Merged: 3/9/2026
Merged by: @timothycarambat

Base: master ← Head: eslint-ci

📝 Commits (1)

  • 782c65f add lint CI GitHub Action

📊 Changes

4 files changed (+76 additions, -1 deletions)

View changed files

➕ .github/workflows/lint.yaml (+72 -0)
📝 collector/package.json (+2 -1)
📝 package.json (+1 -0)
📝 server/package.json (+1 -0)

📄 Description

Pull Request Type

  • 🔨 chore (Build, CI, maintenance)

Relevant Issues

resolves #

Description

Adds a GitHub Actions CI workflow that runs ESLint across all three monorepo projects (server, frontend, collector) on pull requests.

  • Added lint:check scripts to server and collector (eslint without --fix)
  • Added top-level yarn lint:ci script that runs lint:check in all three projects
  • Created .github/workflows/lint.yaml that triggers on PRs touching .js/.jsx source files or ESLint configs
  • The existing yarn lint (with --fix) remains unchanged for local development use

Additional Information

  • The top-level eslint.config.js is not used by this workflow — each project uses its own ESLint config (server/eslint.config.mjs, collector/eslint.config.mjs, frontend/eslint.config.js)
  • frontend already had a lint:check script, so no change was needed there
  • All three projects pass lint:check locally as of this PR

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • I have tested my code functionality

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/5160 **Author:** [@angelplusultra](https://github.com/angelplusultra) **Created:** 3/6/2026 **Status:** ✅ Merged **Merged:** 3/9/2026 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `eslint-ci` --- ### 📝 Commits (1) - [`782c65f`](https://github.com/Mintplex-Labs/anything-llm/commit/782c65fb6af50c052ee4c332a8f7d95800cc05eb) add lint CI GitHub Action ### 📊 Changes **4 files changed** (+76 additions, -1 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/lint.yaml` (+72 -0) 📝 `collector/package.json` (+2 -1) 📝 `package.json` (+1 -0) 📝 `server/package.json` (+1 -0) </details> ### 📄 Description ### Pull Request Type - [x] 🔨 chore (Build, CI, maintenance) ### Relevant Issues resolves # ### Description Adds a GitHub Actions CI workflow that runs ESLint across all three monorepo projects (`server`, `frontend`, `collector`) on pull requests. - Added `lint:check` scripts to `server` and `collector` (`eslint` without `--fix`) - Added top-level `yarn lint:ci` script that runs `lint:check` in all three projects - Created `.github/workflows/lint.yaml` that triggers on PRs touching `.js`/`.jsx` source files or ESLint configs - The existing `yarn lint` (with `--fix`) remains unchanged for local development use ### Additional Information - The top-level `eslint.config.js` is not used by this workflow — each project uses its own ESLint config (`server/eslint.config.mjs`, `collector/eslint.config.mjs`, `frontend/eslint.config.js`) - `frontend` already had a `lint:check` script, so no change was needed there - All three projects pass `lint:check` locally as of this PR ### Developer Validations - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] I have tested my code functionality --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 15:21:00 -04:00
yindo closed this issue 2026-06-05 15:21:00 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5329
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?