Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Need automated Open API syntax validation on submitting PR to master

Open
#366 18 comments 0 reactions 1 assignee View on GitHub

@ravi-prakash-v is already working on this.

Since Oct 30, 2023.

Assessment

This issue has not been assessed yet.

Description

C4GT Community enhancement Protocol Draft

Name: Protocol Specifications
Title: "Need automated Open API syntax validation on submitting PR to master"
Labels: C4GT Community


Description

Problem:
Sometimes when pull requests are merged, syntactical errors in the Open API document get committed on master.

Feature Request
An automated script that runs when creating a PR to the spec. It should validate transaction.yaml, meta.yaml, and registry.yaml against Open API 3.0 specification.

Goals

  • An automated script that runs when creating a PR to the spec. It should validate transaction.yaml, meta.yaml, and registry.yaml against Open API 3.0 specification.

Expected Outcome

  • Specs on master branch should not have any errors

Acceptance Criteria

  • Checks run on a PR with syntax errors in OpenAPI spec should fail
  • Checks run on a PR with no syntax errors in OpenAPI spec should pass

Implementation Details

Mockups / Wireframes


Project

Beckn

Organization Name:

Beckn Open Collective

Domain

Others

Tech Skills Needed:

Open API 3.0
Github actions
Node JS

Mentor(s)

Ravi Prakash

Complexity

Medium

Category

CI/CD

Sub Category

Backend, Research

Dominant language
No language data
Stars
454
Forks
127
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beckn/protocol-specifications

All issues in beckn/protocol-specifications

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.