How to Submit a New Tool to the Awesome Continuous AI List: Complete Submission Process Guide

To submit a new tool to the Awesome Continuous AI list, you must open a structured GitHub issue using the repository's submission template, complete the required metadata fields, confirm compliance with the checklist, and pass automated duplicate detection before maintainer review.

The Awesome Continuous AI repository (githubnext/awesome-continuous-ai) maintains a curated collection of AI-powered development tools. The submission process for new tools is fully automated through GitHub Issues and Actions, ensuring that every proposed entry meets consistent quality and formatting standards before being merged into README.md.

Understanding the Awesome Continuous AI Submission Workflow

The repository uses a GitHub Issue-based workflow defined in CONTRIBUTING.md and enforced through the .github/ISSUE_TEMPLATE/submission.yml form. When you submit a new tool, the repository triggers two automated workflows: .github/workflows/detect-duplicate-tools.yml to check for existing entries and .github/workflows/genai-issue-labeller.yml to assist with categorization. Only after these automated checks pass does a human maintainer review and merge the entry into the public list.

Step-by-Step Guide to the Submission Process for New Tools

Step 1: Initiate the Issue via CONTRIBUTING.md

Navigate to the repository's CONTRIBUTING.md file and click the "Submit a New Resource" button. This link pre-populates a new issue using the submission.yml template and automatically applies the submission label.

The direct URL structure encodes the template and label:

https://github.com/githubnext/awesome-continuous-ai/issues/new?assignees=&labels=submission&projects=&template=submission.yml&title=%5BSUBMISSION%5D+

Step 2: Complete the submission.yml Form Fields

The .github/ISSUE_TEMPLATE/submission.yml template enforces the following required fields:

• Title: The name of the tool
• Description: A concise explanation of the tool's functionality
• URL: The GitHub repository or official website link
• Category: Selected from a dropdown matching the README.md sections (e.g., "Continuous Triage", "Continuous Documentation")

Validation rules (required: true) prevent submission until all fields contain data.

Step 3: Confirm the Compliance Checklist

Before submitting, you must acknowledge three compliance items in the "Submission Guidelines" section:

1. The resource is AI-focused and relevant to continuous software development
2. The resource is publicly accessible
3. The resource is not already listed in the repository

These checkboxes are defined in the terms section of submission.yml.

Step 4: Automated Triage and Duplicate Detection

Upon submission, GitHub Actions immediately process the issue:

1. .github/workflows/detect-duplicate-tools.yml scans existing README.md entries to verify the URL is not already present. If a duplicate is detected, the workflow comments on the issue and may close it automatically.

2. .github/workflows/genai-issue-labeller.yml may add AI-generated labels or summaries to assist maintainers in categorization.

These automated checks ensure repository hygiene before human review begins.

Step 5: Maintainer Review and Merge

After automated validation passes, a maintainer performs the following:

1. Validates the selected category against README.md structure
2. Verifies the description meets style guidelines
3. Creates a pull request that adds the new entry to the appropriate section of README.md

Once the PR is merged, the tool appears in the public Awesome Continuous AI list and the original submission issue is closed.

Key Files in the Submission Process

Understanding these source files helps you navigate the submission process effectively:

File	Purpose
CONTRIBUTING.md	Entry point containing the submission button and high-level guidelines
.github/ISSUE_TEMPLATE/submission.yml	Structured form defining required fields and validation rules
.github/workflows/detect-duplicate-tools.yml	Automated duplicate detection workflow
.github/workflows/genai-issue-labeller.yml	AI-assisted labeling workflow
README.md	The public-facing awesome list updated after approval

Summary

• The submission process for new tools requires opening a GitHub Issue using the structured submission.yml template linked from CONTRIBUTING.md.
• You must provide title, description, URL, and category metadata, plus confirm compliance with the AI-focus and duplication checklists.
• Automated workflows (detect-duplicate-tools.yml and genai-issue-labeller.yml) validate submissions before human review.
• Approved entries are merged into README.md via maintainer pull requests, making them visible in the Awesome Continuous AI list.

Frequently Asked Questions

What information is required when submitting a new tool?

You must complete four mandatory fields defined in .github/ISSUE_TEMPLATE/submission.yml: the tool name (title), a concise description, the public URL, and the category selected from a dropdown menu. Additionally, you must check three compliance boxes confirming the tool is AI-focused, publicly accessible, and not already listed.

How long does the submission process take?

The timeline varies based on maintainer availability, but the automated triage completes within minutes. The .github/workflows/detect-duplicate-tools.yml action runs immediately upon submission to check for existing entries. After automated validation, human review and the subsequent pull request to README.md typically occur within several days to one week.

What happens if my submitted tool is a duplicate?

If .github/workflows/detect-duplicate-tools.yml detects that the URL already exists in README.md, the workflow will automatically comment on your issue indicating the duplication. Depending on the configuration, the issue may be closed automatically or flagged for manual review, preventing redundant entries from cluttering the list.

Can I submit a tool without using the GitHub issue template?

No, the repository enforces structured submissions through .github/ISSUE_TEMPLATE/submission.yml. While you could technically open a blank issue, maintainers will likely redirect you to the proper template because the automated workflows (detect-duplicate-tools.yml and genai-issue-labeller.yml) depend on the standardized metadata fields and submission label to process entries correctly.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}