Code on Producthunt daily

eslint

Wed, 24 Sep 2025 15:28:00 +0800

eslint/eslint

ESLint

ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and JSHint with a few exceptions:

ESLint uses Espree for JavaScript parsing.
ESLint uses an AST to evaluate patterns in code.
ESLint is completely pluggable, every single rule is a plugin and you can add more at runtime.

Installation and Usage

Prerequisites: Node.js (^18.18.0, ^20.9.0, or >=21.1.0) built with SSL support. (If you are using an official Node.js distribution, SSL is always built in.)

You can install and configure ESLint using this command:

`1`	`npm init @eslint/config@latest`

After that, you can run ESLint on any file or directory like this:

`1`	`npx eslint yourfile.js`

pnpm Installation

To use ESLint with pnpm, we recommend setting up a .npmrc file with at least the following settings:

1
2

auto-install-peers=true
node-linker=hoisted

This ensures that pnpm installs dependencies in a way that is more compatible with npm and is less likely to produce errors.

Configuration

You can configure rules in your eslint.config.js files as in this example:

import { defineConfig } from "eslint/config";

export default defineConfig([
	{
		files: ["**/*.js", "**/*.cjs", "**/*.mjs"],
		rules: {
			"prefer-const": "warn",
			"no-constant-binary-expression": "error",
		},
	},
]);

The names "prefer-const" and "no-constant-binary-expression" are the names of rules in ESLint. The first value is the error level of the rule and can be one of these values:

"off" or 0 - turn the rule off
"warn" or 1 - turn the rule on as a warning (doesn’t affect exit code)
"error" or 2 - turn the rule on as an error (exit code will be 1)

The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs).

Version Support

The ESLint team provides ongoing support for the current version and six months of limited support for the previous version. Limited support includes critical bug fixes, security issues, and compatibility issues only.

ESLint offers commercial support for both current and previous versions through our partners, Tidelift and HeroDevs.

See Version Support for more details.

Code of Conduct

ESLint adheres to the OpenJS Foundation Code of Conduct.

Filing Issues

Before filing an issue, please be sure to read the guidelines for what you’re reporting:

Frequently Asked Questions

Does ESLint support JSX?

Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). Please note that supporting JSX syntax is not the same as supporting React. React applies specific semantics to JSX syntax that ESLint doesn’t recognize. We recommend using eslint-plugin-react if you are using React and want React semantics.

Does Prettier replace ESLint?

No, ESLint and Prettier have different jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to Prettier’s documentation to learn how to configure them to work well with each other.

What ECMAScript versions does ESLint support?

ESLint has full support for ECMAScript 3, 5, and every year from 2015 up until the most recent stage 4 specification (the default). You can set your desired ECMAScript syntax and other settings (like global variables) through configuration.

What about experimental features?

ESLint’s parser only officially supports the latest final ECMAScript standard. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis.

In other cases (including if rules need to warn on more or fewer cases due to new syntax, rather than just not crashing), we recommend you use other parsers and/or rule plugins. If you are using Babel, you can use @babel/eslint-parser and @babel/eslint-plugin to use any option available in Babel.

Once a language feature has been adopted into the ECMAScript standard (stage 4 according to the TC39 process), we will accept issues and pull requests related to the new feature, subject to our contributing guidelines. Until then, please use the appropriate parser and plugin(s) for your experimental feature.

Which Node.js versions does ESLint support?

ESLint updates the supported Node.js versions with each major release of ESLint. At that time, ESLint’s supported Node.js versions are updated to be:

The most recent maintenance release of Node.js
The lowest minor version of the Node.js LTS release that includes the features the ESLint team wants to use.
The Node.js Current release

ESLint is also expected to work with Node.js versions released after the Node.js Current release.

Refer to the Quick Start Guide for the officially supported Node.js versions for a given ESLint release.

Where to ask for help?

Open a discussion or stop by our Discord server.

Why doesn’t ESLint lock dependency versions?

Lock files like package-lock.json are helpful for deployed applications. They ensure that dependencies are consistent between environments and across deployments.

Packages like eslint that get published to the npm registry do not include lock files. npm install eslint as a user will respect version constraints in ESLint’s package.json. ESLint and its dependencies will be included in the user’s lock file if one exists, but ESLint’s own lock file would not be used.

We intentionally don’t lock dependency versions so that we have the latest compatible dependency versions in development and CI that our users get when installing ESLint in a project.

The Twilio blog has a deeper dive to learn more.

Releases

We have scheduled releases every two weeks on Friday or Saturday. You can follow a release issue for updates about the scheduling of any particular release.

Security Policy

ESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full security policy.

Semantic Versioning Policy

ESLint follows semantic versioning. However, due to the nature of ESLint as a code quality tool, it’s not always clear when a minor or major version bump occurs. To help clarify this for everyone, we’ve defined the following semantic versioning policy for ESLint:

Patch release (intended to not break your lint build)
- A bug fix in a rule that results in ESLint reporting fewer linting errors.
- A bug fix to the CLI or core (including formatters).
- Improvements to documentation.
- Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
- Re-releasing after a failed release (i.e., publishing a release that doesn’t work for anyone).
Minor release (might break your lint build)
- A bug fix in a rule that results in ESLint reporting more linting errors.
- A new rule is created.
- A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
- A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
- An existing rule is deprecated.
- A new CLI capability is created.
- New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
- A new formatter is created.
- eslint:recommended is updated and will result in strictly fewer linting errors (e.g., rule removals).
Major release (likely to break your lint build)
- eslint:recommended is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
- A new option to an existing rule that results in ESLint reporting more linting errors by default.
- An existing formatter is removed.
- Part of the public API is removed or changed in an incompatible way. The public API includes:
  - Rule schemas
  - Configuration schema
  - Command-line options
  - Node.js API
  - Rule, formatter, parser, plugin APIs

According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (~) in package.json e.g. "eslint": "~3.1.0" to guarantee the results of your builds.

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Team

These folks keep the project moving and are resources for help.

Technical Steering Committee (TSC)

The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.

Nicholas C. Zakas

Francesco Trotta

Milos Djermanovic

Reviewers

The people who review and implement new features.

唯然	Nitin Kumar

Committers

The people who review and fix bugs and help triage issues.

fnx

Josh Goldberg ✨

Tanuj Kanti

루밀LuMir

Website Team

Team members who focus specifically on eslint.org

Amaresh S M

Harish

Percy Ma

ML_course

Sat, 13 Sep 2025 15:24:13 +0800

epfml/ML_course

EPFL Machine Learning Course CS-433

Machine Learning Course, Fall 2023

The course website and syllabus is available here: https://www.epfl.ch/labs/mlo/machine-learning-cs-433/

This repository contains all lecture notes, labs and projects - resources, code templates and solutions.

Videos will be available after each lecture on the mediaspace channel, here for 2022 lectures and for 2022 exercises, and here for 2021.

Contact us if you have any questions, via the discussion forum (for EPFL students), or email to the assistants or teachers. Please create issues and pull requests here using the menu above.

github-mcp-server

Sun, 20 Jul 2025 15:28:48 +0800

github/github-mcp-server

GitHub MCP Server

The GitHub MCP Server connects AI tools directly to GitHub’s platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.

Use Cases

Repository Management: Browse and query code, search files, analyze commits, and understand project structure across any repository you have access to.
Issue & PR Automation: Create, update, and manage issues and pull requests. Let AI help triage bugs, review code changes, and maintain project boards.
CI/CD & Workflow Intelligence: Monitor GitHub Actions workflow runs, analyze build failures, manage releases, and get insights into your development pipeline.
Code Analysis: Examine security findings, review Dependabot alerts, understand code patterns, and get comprehensive insights into your codebase.
Team Collaboration: Access discussions, manage notifications, analyze team activity, and streamline processes for your team.

Built for developers who want to connect their AI tools to GitHub context and capabilities, from simple natural language queries to complex multi-step agent workflows.

Remote GitHub MCP Server

The remote GitHub MCP Server is hosted by GitHub and provides the easiest method for getting up and running. If your MCP host does not support remote MCP servers, don’t worry! You can use the local version of the GitHub MCP Server instead.

Prerequisites

A compatible MCP host with remote server support (VS Code 1.101+, Claude Desktop, Cursor, Windsurf, etc.)
Any applicable policies enabled

Install in VS Code

For quick installation, use one of the one-click install buttons above. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start. Make sure you’re using VS Code 1.101 or later for remote MCP and OAuth support.

Alternatively, to manually configure VS Code, choose the appropriate JSON block from the examples below and add it to your host configuration:

Using OAuth Using a GitHub PAT

VS Code (version 1.101 or greater)

{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}

{
  "servers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/",
      "headers": {
        "Authorization": "Bearer ${input:github_mcp_pat}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "github_mcp_pat",
      "description": "GitHub Personal Access Token",
      "password": true
    }
  ]
}

Install in other MCP hosts

GitHub Copilot in other IDEs - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot
Claude Applications - Installation guide for Claude Web, Claude Desktop and Claude Code CLI
Cursor - Installation guide for Cursor IDE
Windsurf - Installation guide for Windsurf IDE

Note: Each MCP host application needs to configure a GitHub App or OAuth App to support remote access via OAuth. Any host application that supports remote MCP servers should support the remote GitHub server with PAT authentication. Configuration details and support levels vary by host. Make sure to refer to the host application’s documentation for more info.

⚠️ Public Preview Status: The remote GitHub MCP Server is currently in Public Preview. During preview, access may be gated depending on authentication type and surface:

OAuth: Subject to GitHub Copilot Editor Preview Policy until GA

PAT: Controlled via your organization’s PAT policies

MCP Servers in Copilot policy: Enables/disables access to all MCP servers in VS Code, with other Copilot editors migrating to this policy in the coming months.

Configuration

See Remote Server Documentation on how to pass additional configuration settings to the remote GitHub MCP Server.

Local GitHub MCP Server

Prerequisites

To run the server in a container, you will need to have Docker installed.
Once Docker is installed, you will also need to ensure Docker is running. The image is public; if you get errors on pull, you may have an expired token and need to docker logout ghcr.io.
Lastly you will need to Create a GitHub Personal Access Token. The MCP server can use many of the GitHub APIs, so enable the permissions that you feel comfortable granting your AI tools (to learn more about access tokens, please check out the documentation).

Handling PATs Securely

Environment Variables (Recommended)

To keep your GitHub PAT secure and reusable across different MCP hosts:

Store your PAT in environment variables

`1`	`export GITHUB_PAT=your_token_here`

Or create a .env file:

`1`	`GITHUB_PAT=your_token_here`

Protect your .env file

1
2

# Add to .gitignore to prevent accidental commits
echo ".env" >> .gitignore

Reference the token in configurations

# CLI usage
claude mcp update github -e GITHUB_PERSONAL_ACCESS_TOKEN=$GITHUB_PAT

# In config files (where supported)
"env": {
  "GITHUB_PERSONAL_ACCESS_TOKEN": "$GITHUB_PAT"
}

Note: Environment variable support varies by host app and IDE. Some applications (like Windsurf) require hardcoded tokens in config files.

Token Security Best Practices

Minimum scopes: Only grant necessary permissions
- repo - Repository operations
- read:packages - Docker image access
Separate tokens: Use different PATs for different projects/environments
Regular rotation: Update tokens periodically
Never commit: Keep tokens out of version control
File permissions: Restrict access to config files containing tokens
1

chmod 600 ~/.your-app/config.json

Installation

Install in GitHub Copilot on VS Code

For quick installation, use one of the one-click install buttons above. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start.

More about using MCP server tools in VS Code’s agent mode documentation.

Install in GitHub Copilot on other IDEs (JetBrains, Visual Studio, Eclipse, etc.)

Add the following JSON block to your IDE’s MCP settings.

{
  "mcp": {
    "inputs": [
      {
        "type": "promptString",
        "id": "github_token",
        "description": "GitHub Personal Access Token",
        "password": true
      }
    ],
    "servers": {
      "github": {
        "command": "docker",
        "args": [
          "run",
          "-i",
          "--rm",
          "-e",
          "GITHUB_PERSONAL_ACCESS_TOKEN",
          "ghcr.io/github/github-mcp-server"
        ],
        "env": {
          "GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}"
        }
      }
    }
  }
}

Optionally, you can add a similar example (i.e. without the mcp key) to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with other host applications that accept the same format.

Example JSON block without the MCP key included

{
  "inputs": [
    {
      "type": "promptString",
      "id": "github_token",
      "description": "GitHub Personal Access Token",
      "password": true
    }
  ],
  "servers": {
    "github": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "ghcr.io/github/github-mcp-server"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}"
      }
    }
  }
}

Install in Other MCP Hosts

For other MCP host applications, please refer to our installation guides:

GitHub Copilot in other IDEs - Installation for JetBrains, Visual Studio, Eclipse, and Xcode with GitHub Copilot
Claude Code & Claude Desktop - Installation guide for Claude Code and Claude Desktop
Cursor - Installation guide for Cursor IDE
Windsurf - Installation guide for Windsurf IDE

For a complete overview of all installation options, see our Installation Guides Index.

Note: Any host application that supports local MCP servers should be able to access the local GitHub MCP server. However, the specific configuration process, syntax and stability of the integration will vary by host application. While many may follow a similar format to the examples above, this is not guaranteed. Please refer to your host application’s documentation for the correct MCP configuration syntax and setup process.

Build from source

If you don’t have Docker, you can use go build to build the binary in the cmd/github-mcp-server directory, and use the github-mcp-server stdio command with the GITHUB_PERSONAL_ACCESS_TOKEN environment variable set to your token. To specify the output location of the build, use the -o flag. You should configure your server to use the built executable as its command. For example:

{
  "mcp": {
    "servers": {
      "github": {
        "command": "/path/to/github-mcp-server",
        "args": ["stdio"],
        "env": {
          "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
        }
      }
    }
  }
}

Tool Configuration

The GitHub MCP Server supports enabling or disabling specific groups of functionalities via the --toolsets flag. This allows you to control which GitHub API capabilities are available to your AI tools. Enabling only the toolsets that you need can help the LLM with tool choice and reduce the context size.

Toolsets are not limited to Tools. Relevant MCP Resources and Prompts are also included where applicable.

Available Toolsets

The following sets of tools are available (all are on by default):

Toolset	Description
`context`	Strongly recommended: Tools that provide context about the current user and GitHub context you are operating in
`actions`	GitHub Actions workflows and CI/CD operations
`code_security`	Code security related tools, such as GitHub Code Scanning
`dependabot`	Dependabot tools
`discussions`	GitHub Discussions related tools
`experiments`	Experimental features that are not considered stable yet
`issues`	GitHub Issues related tools
`notifications`	GitHub Notifications related tools
`orgs`	GitHub Organization related tools
`pull_requests`	GitHub Pull Request related tools
`repos`	GitHub Repository related tools
`secret_protection`	Secret protection related tools, such as GitHub Secret Scanning
`users`	GitHub User related tools

Tools

Actions

cancel_workflow_run - Cancel workflow run
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
delete_workflow_run_logs - Delete workflow logs
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
download_workflow_run_artifact - Download workflow artifact
- artifact_id: The unique identifier of the artifact (number, required)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
get_job_logs - Get job logs
- failed_only: When true, gets logs for all failed jobs in run_id (boolean, optional)
- job_id: The unique identifier of the workflow job (required for single job logs) (number, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- return_content: Returns actual log content instead of URLs (boolean, optional)
- run_id: Workflow run ID (required when using failed_only) (number, optional)
- tail_lines: Number of lines to return from the end of the log (number, optional)
get_workflow_run - Get workflow run
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
get_workflow_run_logs - Get workflow run logs
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
get_workflow_run_usage - Get workflow usage
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
list_workflow_jobs - List workflow jobs
- filter: Filters jobs by their completed_at timestamp (string, optional)
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
list_workflow_run_artifacts - List workflow artifacts
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
list_workflow_runs - List workflow runs
- actor: Returns someone’s workflow runs. Use the login for the user who created the workflow run. (string, optional)
- branch: Returns workflow runs associated with a branch. Use the name of the branch. (string, optional)
- event: Returns workflow runs for a specific event type (string, optional)
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- status: Returns workflow runs with the check run status (string, optional)
- workflow_id: The workflow ID or workflow file name (string, required)
list_workflows - List workflows
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
rerun_failed_jobs - Rerun failed jobs
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
rerun_workflow_run - Rerun workflow run
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- run_id: The unique identifier of the workflow run (number, required)
run_workflow - Run workflow
- inputs: Inputs the workflow accepts (object, optional)
- owner: Repository owner (string, required)
- ref: The git reference for the workflow. The reference can be a branch or tag name. (string, required)
- repo: Repository name (string, required)
- workflow_id: The workflow ID (numeric) or workflow file name (e.g., main.yml, ci.yaml) (string, required)

Code Security

get_code_scanning_alert - Get code scanning alert
- alertNumber: The number of the alert. (number, required)
- owner: The owner of the repository. (string, required)
- repo: The name of the repository. (string, required)
list_code_scanning_alerts - List code scanning alerts
- owner: The owner of the repository. (string, required)
- ref: The Git reference for the results you want to list. (string, optional)
- repo: The name of the repository. (string, required)
- severity: Filter code scanning alerts by severity (string, optional)
- state: Filter code scanning alerts by state. Defaults to open (string, optional)
- tool_name: The name of the tool used for code scanning. (string, optional)

Context

get_me - Get my user profile
- No parameters required

Dependabot

get_dependabot_alert - Get dependabot alert
- alertNumber: The number of the alert. (number, required)
- owner: The owner of the repository. (string, required)
- repo: The name of the repository. (string, required)
list_dependabot_alerts - List dependabot alerts
- owner: The owner of the repository. (string, required)
- repo: The name of the repository. (string, required)
- severity: Filter dependabot alerts by severity (string, optional)
- state: Filter dependabot alerts by state. Defaults to open (string, optional)

Discussions

get_discussion - Get discussion
- discussionNumber: Discussion Number (number, required)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
get_discussion_comments - Get discussion comments
- discussionNumber: Discussion Number (number, required)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
list_discussion_categories - List discussion categories
- after: Cursor for pagination, use the ‘after’ field from the previous response (string, optional)
- before: Cursor for pagination, use the ‘before’ field from the previous response (string, optional)
- first: Number of categories to return per page (min 1, max 100) (number, optional)
- last: Number of categories to return from the end (min 1, max 100) (number, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
list_discussions - List discussions
- category: Optional filter by discussion category ID. If provided, only discussions with this category are listed. (string, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)

Issues

add_issue_comment - Add comment to issue
- body: Comment content (string, required)
- issue_number: Issue number to comment on (number, required)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
assign_copilot_to_issue - Assign Copilot to issue
- issueNumber: Issue number (number, required)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
create_issue - Open new issue
- assignees: Usernames to assign to this issue (string[], optional)
- body: Issue body content (string, optional)
- labels: Labels to apply to this issue (string[], optional)
- milestone: Milestone number (number, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- title: Issue title (string, required)
get_issue - Get issue details
- issue_number: The number of the issue (number, required)
- owner: The owner of the repository (string, required)
- repo: The name of the repository (string, required)
get_issue_comments - Get issue comments
- issue_number: Issue number (number, required)
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
list_issues - List issues
- direction: Sort direction (string, optional)
- labels: Filter by labels (string[], optional)
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- since: Filter by date (ISO 8601 timestamp) (string, optional)
- sort: Sort order (string, optional)
- state: Filter by state (string, optional)
search_issues - Search issues
- order: Sort order (string, optional)
- owner: Optional repository owner. If provided with repo, only notifications for this repository are listed. (string, optional)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- query: Search query using GitHub issues search syntax (string, required)
- repo: Optional repository name. If provided with owner, only notifications for this repository are listed. (string, optional)
- sort: Sort field by number of matches of categories, defaults to best match (string, optional)
update_issue - Edit issue
- assignees: New assignees (string[], optional)
- body: New description (string, optional)
- issue_number: Issue number to update (number, required)
- labels: New labels (string[], optional)
- milestone: New milestone number (number, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- state: New state (string, optional)
- title: New title (string, optional)

Notifications

dismiss_notification - Dismiss notification
- state: The new state of the notification (read/done) (string, optional)
- threadID: The ID of the notification thread (string, required)
get_notification_details - Get notification details
- notificationID: The ID of the notification (string, required)
list_notifications - List notifications
- before: Only show notifications updated before the given time (ISO 8601 format) (string, optional)
- filter: Filter notifications to, use default unless specified. Read notifications are ones that have already been acknowledged by the user. Participating notifications are those that the user is directly involved in, such as issues or pull requests they have commented on or created. (string, optional)
- owner: Optional repository owner. If provided with repo, only notifications for this repository are listed. (string, optional)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Optional repository name. If provided with owner, only notifications for this repository are listed. (string, optional)
- since: Only show notifications updated after the given time (ISO 8601 format) (string, optional)
manage_notification_subscription - Manage notification subscription
- action: Action to perform: ignore, watch, or delete the notification subscription. (string, required)
- notificationID: The ID of the notification thread. (string, required)
manage_repository_notification_subscription - Manage repository notification subscription
- action: Action to perform: ignore, watch, or delete the repository notification subscription. (string, required)
- owner: The account owner of the repository. (string, required)
- repo: The name of the repository. (string, required)
mark_all_notifications_read - Mark all notifications as read
- lastReadAt: Describes the last point that notifications were checked (optional). Default: Now (string, optional)
- owner: Optional repository owner. If provided with repo, only notifications for this repository are marked as read. (string, optional)
- repo: Optional repository name. If provided with owner, only notifications for this repository are marked as read. (string, optional)

Organizations

search_orgs - Search organizations
- order: Sort order (string, optional)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- query: Search query using GitHub organizations search syntax scoped to type:org (string, required)
- sort: Sort field by category (string, optional)

Pull Requests

add_comment_to_pending_review - Add review comment to the requester’s latest pending pull request review
- body: The text of the review comment (string, required)
- line: The line of the blob in the pull request diff that the comment applies to. For multi-line comments, the last line of the range (number, optional)
- owner: Repository owner (string, required)
- path: The relative path to the file that necessitates a comment (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
- side: The side of the diff to comment on. LEFT indicates the previous state, RIGHT indicates the new state (string, optional)
- startLine: For multi-line comments, the first line of the range that the comment applies to (number, optional)
- startSide: For multi-line comments, the starting side of the diff that the comment applies to. LEFT indicates the previous state, RIGHT indicates the new state (string, optional)
- subjectType: The level at which the comment is targeted (string, required)
create_and_submit_pull_request_review - Create and submit a pull request review without comments
- body: Review comment text (string, required)
- commitID: SHA of commit to review (string, optional)
- event: Review action to perform (string, required)
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
create_pending_pull_request_review - Create pending pull request review
- commitID: SHA of commit to review (string, optional)
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
create_pull_request - Open new pull request
- base: Branch to merge into (string, required)
- body: PR description (string, optional)
- draft: Create as draft PR (boolean, optional)
- head: Branch containing changes (string, required)
- maintainer_can_modify: Allow maintainer edits (boolean, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- title: PR title (string, required)
delete_pending_pull_request_review - Delete the requester’s latest pending pull request review
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
get_pull_request - Get pull request details
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
get_pull_request_comments - Get pull request comments
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
get_pull_request_diff - Get pull request diff
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
get_pull_request_files - Get pull request files
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
get_pull_request_reviews - Get pull request reviews
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
get_pull_request_status - Get pull request status checks
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
list_pull_requests - List pull requests
- base: Filter by base branch (string, optional)
- direction: Sort direction (string, optional)
- head: Filter by head user/org and branch (string, optional)
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- sort: Sort by (string, optional)
- state: Filter by state (string, optional)
merge_pull_request - Merge pull request
- commit_message: Extra detail for merge commit (string, optional)
- commit_title: Title for merge commit (string, optional)
- merge_method: Merge method (string, optional)
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
request_copilot_review - Request Copilot review
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
search_pull_requests - Search pull requests
- order: Sort order (string, optional)
- owner: Optional repository owner. If provided with repo, only notifications for this repository are listed. (string, optional)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- query: Search query using GitHub pull request search syntax (string, required)
- repo: Optional repository name. If provided with owner, only notifications for this repository are listed. (string, optional)
- sort: Sort field by number of matches of categories, defaults to best match (string, optional)
submit_pending_pull_request_review - Submit the requester’s latest pending pull request review
- body: The text of the review comment (string, optional)
- event: The event to perform (string, required)
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)
update_pull_request - Edit pull request
- base: New base branch name (string, optional)
- body: New description (string, optional)
- maintainer_can_modify: Allow maintainer edits (boolean, optional)
- owner: Repository owner (string, required)
- pullNumber: Pull request number to update (number, required)
- repo: Repository name (string, required)
- state: New state (string, optional)
- title: New title (string, optional)
update_pull_request_branch - Update pull request branch
- expectedHeadSha: The expected SHA of the pull request’s HEAD ref (string, optional)
- owner: Repository owner (string, required)
- pullNumber: Pull request number (number, required)
- repo: Repository name (string, required)

Repositories

create_branch - Create branch
- branch: Name for new branch (string, required)
- from_branch: Source branch (defaults to repo default) (string, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
create_or_update_file - Create or update file
- branch: Branch to create/update the file in (string, required)
- content: Content of the file (string, required)
- message: Commit message (string, required)
- owner: Repository owner (username or organization) (string, required)
- path: Path where to create/update the file (string, required)
- repo: Repository name (string, required)
- sha: Required if updating an existing file. The blob SHA of the file being replaced. (string, optional)
create_repository - Create repository
- autoInit: Initialize with README (boolean, optional)
- description: Repository description (string, optional)
- name: Repository name (string, required)
- private: Whether repo should be private (boolean, optional)
delete_file - Delete file
- branch: Branch to delete the file from (string, required)
- message: Commit message (string, required)
- owner: Repository owner (username or organization) (string, required)
- path: Path to the file to delete (string, required)
- repo: Repository name (string, required)
fork_repository - Fork repository
- organization: Organization to fork to (string, optional)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
get_commit - Get commit details
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- sha: Commit SHA, branch name, or tag name (string, required)
get_file_contents - Get file or directory contents
- owner: Repository owner (username or organization) (string, required)
- path: Path to file/directory (directories must end with a slash ‘/’) (string, optional)
- ref: Accepts optional git refs such as refs/tags/{tag}, refs/heads/{branch} or refs/pull/{pr_number}/head (string, optional)
- repo: Repository name (string, required)
- sha: Accepts optional commit SHA. If specified, it will be used instead of ref (string, optional)
get_tag - Get tag details
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
- tag: Tag name (string, required)
list_branches - List branches
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
list_commits - List commits
- author: Author username or email address to filter commits by (string, optional)
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
- sha: Commit SHA, branch or tag name to list commits of. If not provided, uses the default branch of the repository. If a commit SHA is provided, will list commits up to that SHA. (string, optional)
list_tags - List tags
- owner: Repository owner (string, required)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- repo: Repository name (string, required)
push_files - Push files to repository
- branch: Branch to push to (string, required)
- files: Array of file objects to push, each object with path (string) and content (string) (object[], required)
- message: Commit message (string, required)
- owner: Repository owner (string, required)
- repo: Repository name (string, required)
search_code - Search code
- order: Sort order (string, optional)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- q: Search query using GitHub code search syntax (string, required)
- sort: Sort field (‘indexed’ only) (string, optional)
search_repositories - Search repositories
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- query: Search query (string, required)

Secret Protection

get_secret_scanning_alert - Get secret scanning alert
- alertNumber: The number of the alert. (number, required)
- owner: The owner of the repository. (string, required)
- repo: The name of the repository. (string, required)
list_secret_scanning_alerts - List secret scanning alerts
- owner: The owner of the repository. (string, required)
- repo: The name of the repository. (string, required)
- resolution: Filter by resolution (string, optional)
- secret_type: A comma-separated list of secret types to return. All default secret patterns are returned. To return generic patterns, pass the token name(s) in the parameter. (string, optional)
- state: Filter by state (string, optional)

Users

search_users - Search users
- order: Sort order (string, optional)
- page: Page number for pagination (min 1) (number, optional)
- perPage: Results per page for pagination (min 1, max 100) (number, optional)
- query: Search query using GitHub users search syntax scoped to type:user (string, required)
- sort: Sort field by category (string, optional)

Additional Tools in Remote Github MCP Server

Copilot coding agent

create_pull_request_with_copilot - Perform task with GitHub Copilot coding agent
- owner: Repository owner. You can guess the owner, but confirm it with the user before proceeding. (string, required)
- repo: Repository name. You can guess the repository name, but confirm it with the user before proceeding. (string, required)
- problem_statement: Detailed description of the task to be performed (e.g., ‘Implement a feature that does X’, ‘Fix bug Y’, etc.) (string, required)
- title: Title for the pull request that will be created (string, required)
- base_ref: Git reference (e.g., branch) that the agent will start its work from. If not specified, defaults to the repository’s default branch (string, optional)

Specifying Toolsets

To specify toolsets you want available to the LLM, you can pass an allow-list in two ways:

Using Command Line Argument:

`1`	`github-mcp-server --toolsets repos,issues,pull_requests,actions,code_security`

Using Environment Variable:

`1`	`GITHUB_TOOLSETS="repos,issues,pull_requests,actions,code_security" ./github-mcp-server`

The environment variable GITHUB_TOOLSETS takes precedence over the command line argument if both are provided.

Using Toolsets With Docker

When using Docker, you can pass the toolsets as environment variables:

docker run -i --rm \
  -e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
  -e GITHUB_TOOLSETS="repos,issues,pull_requests,actions,code_security,experiments" \
  ghcr.io/github/github-mcp-server

The “all” Toolset

The special toolset all can be provided to enable all available toolsets regardless of any other configuration:

`1`	`./github-mcp-server --toolsets all`

Or using the environment variable:

`1`	`GITHUB_TOOLSETS="all" ./github-mcp-server`

Dynamic Tool Discovery

Note: This feature is currently in beta and may not be available in all environments. Please test it out and let us know if you encounter any issues.

Instead of starting with all tools enabled, you can turn on dynamic toolset discovery. Dynamic toolsets allow the MCP host to list and enable toolsets in response to a user prompt. This should help to avoid situations where the model gets confused by the sheer number of tools available.

Using Dynamic Tool Discovery

When using the binary, you can pass the --dynamic-toolsets flag.

`1`	`./github-mcp-server --dynamic-toolsets`

When using Docker, you can pass the toolsets as environment variables:

docker run -i --rm \
  -e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
  -e GITHUB_DYNAMIC_TOOLSETS=1 \
  ghcr.io/github/github-mcp-server

Read-Only Mode

To run the server in read-only mode, you can use the --read-only flag. This will only offer read-only tools, preventing any modifications to repositories, issues, pull requests, etc.

`1`	`./github-mcp-server --read-only`

When using Docker, you can pass the read-only mode as an environment variable:

docker run -i --rm \
  -e GITHUB_PERSONAL_ACCESS_TOKEN=<your-token> \
  -e GITHUB_READ_ONLY=1 \
  ghcr.io/github/github-mcp-server

GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com)

The flag --gh-host and the environment variable GITHUB_HOST can be used to set the hostname for GitHub Enterprise Server or GitHub Enterprise Cloud with data residency.

For GitHub Enterprise Server, prefix the hostname with the https:// URI scheme, as it otherwise defaults to http://, which GitHub Enterprise Server does not support.
For GitHub Enterprise Cloud with data residency, use https://YOURSUBDOMAIN.ghe.com as the hostname.

"github": {
    "command": "docker",
    "args": [
    "run",
    "-i",
    "--rm",
    "-e",
    "GITHUB_PERSONAL_ACCESS_TOKEN",
    "-e",
    "GITHUB_HOST",
    "ghcr.io/github/github-mcp-server"
    ],
    "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github_token}",
        "GITHUB_HOST": "https://<your GHES or ghe.com domain name>"
    }
}

i18n / Overriding Descriptions

The descriptions of the tools can be overridden by creating a github-mcp-server-config.json file in the same directory as the binary.

The file should contain a JSON object with the tool names as keys and the new descriptions as values. For example:

{
  "TOOL_ADD_ISSUE_COMMENT_DESCRIPTION": "an alternative description",
  "TOOL_CREATE_BRANCH_DESCRIPTION": "Create a new branch in a GitHub repository"
}

You can create an export of the current translations by running the binary with the --export-translations flag.

This flag will preserve any translations/overrides you have made, while adding any new translations that have been added to the binary since the last time you exported.

1
2

./github-mcp-server --export-translations
cat github-mcp-server-config.json

You can also use ENV vars to override the descriptions. The environment variable names are the same as the keys in the JSON file, prefixed with GITHUB_MCP_ and all uppercase.

For example, to override the TOOL_ADD_ISSUE_COMMENT_DESCRIPTION tool, you can set the following environment variable:

`1`	`export GITHUB_MCP_TOOL_ADD_ISSUE_COMMENT_DESCRIPTION="an alternative description"`

Library Usage

The exported Go API of this module should currently be considered unstable, and subject to breaking changes. In the future, we may offer stability; please file an issue if there is a use case where this would be valuable.

License

This project is licensed under the terms of the MIT open source license. Please refer to MIT for the full terms.

refact

Tue, 08 Jul 2025 15:32:21 +0800

smallcloudai/refact

Refact - Open Sourced AI Software Development Agent

Refact.ai is the #1 open-source AI Agent in SWE-bench verified that handles engineering tasks end-to-end. It deeply understands your codebases and integrates with your tools, databases, and browsers to automate complex, multi-step tasks.

🚀 Seamless Integration with Your Workflow

Refact Agent works effortlessly with the tools and databases you already use:

📁 Version Control: GitHub, GitLab
🗄️ Databases: PostgreSQL, MySQL
🛠️ Debugging: Pdb
🐳 Containerization: Docker

⚡ Why Choose Refact Agent?

✅ Deploy On-Premise: For maximum security, choose our self-hosted AI Agent version and run it on your own infrastructure.
🧠 Access State-of-the-Art Models: Use Claude 4, GPT-4o, or GPT-4o mini with AI Agent or for chat queries.
🔑 Bring Your Own Key (BYOK): Connect your API key and use any LLM: Gemini, Grok, OpenAI, Deepseek, and others.
💬 Integrated IDE Chat: Integrate with GitHub, PostgreSQL, Docker, and more. Refact.ai Agent accesses your resources and handles related operations autonomously, mimicking your workflow.
⚡ Free, Unlimited, Context-Aware Auto-Completion: Code faster with smart AI suggestions.
🛠️ Supports 25+ Programming Languages: Python, JavaScript, Java, Rust, TypeScript, PHP, C++, C#, Go, and many more!

🎉 Hear from our Community

Our Ambassadors shared remarkable stories of how they transform weeks of coding into minutes with Refact.ai Agent!

1️. How Refact.ai built 99.9% of an IoT cloud app Read

2️. How AI-coded prototypes help UX teams deliver real value Read

3️. 80 hours of building from scratch — instead done in 30 minutes Read more

4️. 3 weeks of waiting for a functional GUI? Built in just 14 minutes Read more

Built an automated SEO Content Generator in 60 minutes with Refact.ai Read more

📜 View Full List of Supported Models

📢 Using AI for work? Let’s bring it to your company!

Fill out this form — Our AI Agent will be tailored to your company’s data, learning from feedback, and helping organize knowledge for better collaboration with your team.

📚 Table of Contents

🚀 Core Features and Functionality
🤖 Which Tasks Can Refact Help You With?
⚙️ QuickStart
🐳 Running Refact Self-Hosted in a Docker Container
🔌 Getting Started with Plugins
📖 Documentation
🥇 Contribution
🎉 Join the Community

🚀 Core Features and Functionality

✅ Unlimited accurate auto-completion with context awareness – Powered by Qwen2.5-Coder-1.5B, utilizing Retrieval-Augmented Generation (RAG).

✅ Integrated in-IDE Chat – AI deeply understands your code and provides relevant, intelligent answers.

✅ Integrated with Tools – Works with GitHub, GitLab, PostgreSQL, MySQL, Pdb, Docker, and shell commands.

✅ State-of-the-Art Models – Use Claude 4, GPT-4o, or GPT-4o mini with AI Agent or for chat queries.

✅ Bring Your Own Key (BYOK) – Use your own API keys for external LLMs.

🤖 Which Tasks Can Refact Help You With?

🏗 Generate code from natural language prompts (even with typos).
🔄 Refactor code for better quality and readability.
📖 Explain code to quickly understand unfamiliar code.
🐞 Debug code to detect and fix errors faster.
🧪 Generate unit tests for reliable code.
📌 Code Review with AI-assisted suggestions.
📜 Create Documentation to keep knowledge up to date.
🏷 Generate Docstrings for structured documentation.

⚙️ QuickStart

You can install the Refact repository without Docker:

`1`	`pip install .`

For GPU with CUDA capability >= 8.0 and flash-attention v2 support:

`1`	`FLASH_ATTENTION_FORCE_BUILD=TRUE MAX_JOBS=4 INSTALL_OPTIONAL=TRUE pip install .`

🐳 Running Refact Self-Hosted in a Docker Container

The easiest way to run the self-hosted server is using a pre-built Docker image.
See CONTRIBUTING.md for installation without a Docker container.

🔌 Getting Started with Plugins

Download Refact for VS Code or JetBrains.
Set up a custom inference URL:
1

http://127.0.0.1:8008
Configure the plugin settings:
- JetBrains: Settings > Tools > Refact.ai > Advanced > Inference URL
- VSCode: Extensions > Refact.ai Assistant > Settings > Address URL

📖 Documentation

For detailed guidance and best practices, check out our documentation.

🥇 Contribution

Want to contribute to our project? We’re always open to new ideas and features!

Check out GitHub Issues – See what we’re working on or suggest your own ideas.
Read our Contributing Guide – Check out Contributing.md to get started.

Your contributions help shape the future of Refact Agent! 🚀

⭐ Star History

🎉 Join the Community

We’re all about open-source and empowering developers with AI tools. Our vision is to build the future of programming. Join us and be part of the journey!

📢 Join our Discord server – A community-run space for discussion, questions, and feedback.

Made with ❤️ by developers who automate the boring, so you can focus on building the future.

gitingest

Mon, 23 Jun 2025 15:32:10 +0800

cyclotruc/gitingest

Gitingest

Turn any Git repository into a prompt-friendly text ingest for LLMs.

You can also replace hub with ingest in any GitHub URL to access the corresponding digest.

gitingest.com · Chrome Extension · Firefox Add-on

🚀 Features

Easy code context: Get a text digest from a Git repository URL or a directory
Smart Formatting: Optimized output format for LLM prompts
Statistics about:
- File and directory structure
- Size of the extract
- Token count
CLI tool: Run it as a shell command
Python package: Import it in your code

📚 Requirements

Python 3.8+
For private repositories: A GitHub Personal Access Token (PAT). You can generate one at https://github.com/settings/personal-access-tokens (Profile → Settings → Developer Settings → Personal Access Tokens → Fine-grained Tokens)

📦 Installation

Gitingest is available on PyPI. You can install it using pip:

`1`	`pip install gitingest`

However, it might be a good idea to use pipx to install it. You can install pipx using your preferred package manager.

brew install pipx
apt install pipx
scoop install pipx
...

If you are using pipx for the first time, run:

`1`	`pipx ensurepath`

1
2

# install gitingest
pipx install gitingest

🧩 Browser Extension Usage

The extension is open source at lcandy2/gitingest-extension.

Issues and feature requests are welcome to the repo.

💡 Command line usage

The gitingest command line tool allows you to analyze codebases and create a text dump of their contents.

# Basic usage (writes to digest.txt by default)
gitingest /path/to/directory

# From URL
gitingest https://github.com/cyclotruc/gitingest

# or from specific subdirectory
gitingest https://github.com/cyclotruc/gitingest/tree/main/src/gitingest/utils

For private repositories, use the --token/-t option.

# Get your token from https://github.com/settings/personal-access-tokens
gitingest https://github.com/username/private-repo --token github_pat_...

# Or set it as an environment variable
export GITHUB_TOKEN=github_pat_...
gitingest https://github.com/username/private-repo

By default, the digest is written to a text file (digest.txt) in your current working directory. You can customize the output in two ways:

Use --output/-o <filename> to write to a specific file.
Use --output/-o - to output directly to STDOUT (useful for piping to other tools).

See more options and usage details with:

`1`	`gitingest --help`

🐍 Python package usage

# Synchronous usage
from gitingest import ingest

summary, tree, content = ingest("path/to/directory")

# or from URL
summary, tree, content = ingest("https://github.com/cyclotruc/gitingest")

# or from a specific subdirectory
summary, tree, content = ingest("https://github.com/cyclotruc/gitingest/tree/main/src/gitingest/utils")

For private repositories, you can pass a token:

# Using token parameter
summary, tree, content = ingest("https://github.com/username/private-repo", token="github_pat_...")

# Or set it as an environment variable
import os
os.environ["GITHUB_TOKEN"] = "github_pat_..."
summary, tree, content = ingest("https://github.com/username/private-repo")

By default, this won’t write a file but can be enabled with the output argument.

# Asynchronous usage
from gitingest import ingest_async
import asyncio

result = asyncio.run(ingest_async("path/to/directory"))

Jupyter notebook usage

from gitingest import ingest_async

# Use await directly in Jupyter
summary, tree, content = await ingest_async("path/to/directory")

This is because Jupyter notebooks are asynchronous by default.

🐳 Self-host

Build the image:
1

docker build -t gitingest .

Run the container:

`1`	`docker run -d --name gitingest -p 8000:8000 gitingest`

The application will be available at http://localhost:8000.

If you are hosting it on a domain, you can specify the allowed hostnames via env variable ALLOWED_HOSTS.

1
2

# Default: "gitingest.com, *.gitingest.com, localhost, 127.0.0.1".
ALLOWED_HOSTS="example.com, localhost, 127.0.0.1"

🤝 Contributing

Non-technical ways to contribute

Create an Issue: If you find a bug or have an idea for a new feature, please create an issue on GitHub. This will help us track and prioritize your request.
Spread the Word: If you like Gitingest, please share it with your friends, colleagues, and on social media. This will help us grow the community and make Gitingest even better.
Use Gitingest: The best feedback comes from real-world usage! If you encounter any issues or have ideas for improvement, please let us know by creating an issue on GitHub or by reaching out to us on Discord.

Technical ways to contribute

Gitingest aims to be friendly for first time contributors, with a simple Python and HTML codebase. If you need any help while working with the code, reach out to us on Discord. For detailed instructions on how to make a pull request, see CONTRIBUTING.md.

🛠️ Stack

Tailwind CSS - Frontend
FastAPI - Backend framework
Jinja2 - HTML templating
tiktoken - Token estimation
posthog - Amazing analytics

Looking for a JavaScript/FileSystemNode package?

Check out the NPM alternative 📦 Repomix: https://github.com/yamadashy/repomix

🚀 Project Growth

OpenHands

Sun, 25 May 2025 15:25:59 +0800

All-Hands-AI/OpenHands

OpenHands: Code Less, Make More

Welcome to OpenHands (formerly OpenDevin), a platform for software development agents powered by AI.

OpenHands agents can do anything a human developer can: modify code, run commands, browse the web, call APIs, and yes—even copy code snippets from StackOverflow.

Learn more at docs.all-hands.dev, or sign up for OpenHands Cloud to get started.

[!IMPORTANT] Using OpenHands for work? We’d love to chat! Fill out this short form to join our Design Partner program, where you’ll get early access to commercial features and the opportunity to provide input on our product roadmap.

☁️ OpenHands Cloud

The easiest way to get started with OpenHands is on OpenHands Cloud, which comes with $50 in free credits for new users.

💻 Running OpenHands Locally

OpenHands can also run on your local system using Docker. See the Running OpenHands guide for system requirements and more information.

[!WARNING] On a public network? See our Hardened Docker Installation Guide to secure your deployment by restricting network binding and implementing additional security measures.

docker pull docker.all-hands.dev/all-hands-ai/runtime:0.39-nikolaik

docker run -it --rm --pull=always \
    -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:0.39-nikolaik \
    -e LOG_ALL_EVENTS=true \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v ~/.openhands-state:/.openhands-state \
    -p 3000:3000 \
    --add-host host.docker.internal:host-gateway \
    --name openhands-app \
    docker.all-hands.dev/all-hands-ai/openhands:0.39

You’ll find OpenHands running at http://localhost:3000!

When you open the application, you’ll be asked to choose an LLM provider and add an API key. Anthropic’s Claude Sonnet 4 (anthropic/claude-sonnet-4-20250514) works best, but you have many options.

💡 Other ways to run OpenHands

[!CAUTION] OpenHands is meant to be run by a single user on their local workstation. It is not appropriate for multi-tenant deployments where multiple users share the same instance. There is no built-in authentication, isolation, or scalability.

If you’re interested in running OpenHands in a multi-tenant environment, please get in touch with us for advanced deployment options.

You can also connect OpenHands to your local filesystem, run OpenHands in a scriptable headless mode, interact with it via a friendly CLI, or run it on tagged issues with a github action.

Visit Running OpenHands for more information and setup instructions.

If you want to modify the OpenHands source code, check out Development.md.

Having issues? The Troubleshooting Guide can help.

📖 Documentation

To learn more about the project, and for tips on using OpenHands, check out our documentation.

There you’ll find resources on how to use different LLM providers, troubleshooting resources, and advanced configuration options.

🤝 How to Join the Community

OpenHands is a community-driven project, and we welcome contributions from everyone. We do most of our communication through Slack, so this is the best place to start, but we also are happy to have you contact us on Discord or Github:

Join our Slack workspace - Here we talk about research, architecture, and future development.
Join our Discord server - This is a community-run server for general discussion, questions, and feedback.
Read or post Github Issues - Check out the issues we’re working on, or add your own ideas.

See more about the community in COMMUNITY.md or find details on contributing in CONTRIBUTING.md.

📈 Progress

See the monthly OpenHands roadmap here (updated at the maintainer’s meeting at the end of each month).

📜 License

Distributed under the MIT License. See LICENSE for more information.

🙏 Acknowledgements

OpenHands is built by a large number of contributors, and every contribution is greatly appreciated! We also build upon other open source projects, and we are deeply thankful for their work.

For a list of open source projects and licenses used in OpenHands, please see our CREDITS.md file.

📚 Cite

@misc{openhands,
      title={{OpenHands: An Open Platform for AI Software Developers as Generalist Agents}},
      author={Xingyao Wang and Boxuan Li and Yufan Song and Frank F. Xu and Xiangru Tang and Mingchen Zhuge and Jiayi Pan and Yueqi Song and Bowen Li and Jaskirat Singh and Hoang H. Tran and Fuqiang Li and Ren Ma and Mingzhang Zheng and Bill Qian and Yanjun Shao and Niklas Muennighoff and Yizhe Zhang and Binyuan Hui and Junyang Lin and Robert Brennan and Hao Peng and Heng Ji and Graham Neubig},
      year={2024},
      eprint={2407.16741},
      archivePrefix={arXiv},
      primaryClass={cs.SE},
      url={https://arxiv.org/abs/2407.16741},
}

Code on Producthunt daily

eslint

eslint/eslint

ESLint

Table of Contents

Installation and Usage

pnpm Installation

Configuration

Version Support

Code of Conduct

Filing Issues

Frequently Asked Questions

Does ESLint support JSX?

Does Prettier replace ESLint?

What ECMAScript versions does ESLint support?

What about experimental features?

Which Node.js versions does ESLint support?

Where to ask for help?

Why doesn’t ESLint lock dependency versions?

Releases

Security Policy

Semantic Versioning Policy

License

Team

Technical Steering Committee (TSC)

Reviewers

Committers

Website Team

Sponsors

Platinum Sponsors

Gold Sponsors

Silver Sponsors

Bronze Sponsors

Technology Sponsors

ML_course

epfml/ML_course

EPFL Machine Learning Course CS-433

github-mcp-server

github/github-mcp-server

GitHub MCP Server

Use Cases

Remote GitHub MCP Server

Prerequisites

Install in VS Code

Install in other MCP hosts

Configuration

Local GitHub MCP Server

Prerequisites

Environment Variables (Recommended)

Token Security Best Practices

Installation

Install in GitHub Copilot on VS Code

Install in Other MCP Hosts

Build from source

Tool Configuration

Available Toolsets

Tools

Additional Tools in Remote Github MCP Server

Specifying Toolsets

Using Toolsets With Docker

The “all” Toolset

Dynamic Tool Discovery

Using Dynamic Tool Discovery

Read-Only Mode

GitHub Enterprise Server and Enterprise Cloud with data residency (ghe.com)

i18n / Overriding Descriptions

Library Usage

License

refact

smallcloudai/refact

Refact - Open Sourced AI Software Development Agent

🚀 Seamless Integration with Your Workflow

⚡ Why Choose Refact Agent?

🎉 Hear from our Community

📚 Table of Contents

🚀 Core Features and Functionality

🤖 Which Tasks Can Refact Help You With?

⚙️ QuickStart

🐳 Running Refact Self-Hosted in a Docker Container

🔌 Getting Started with Plugins