swagger-api / swagger-api/swagger-codegen

Review CI coverage

Open
#4,966 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: CI/Test
Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

Currently, not all generates are tested and this thread aims to review what can be tested but not yet added to CIs (travis, appveyor, shippable)

Swagger-codegen version

Latest master

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the existing CI configurations for Travis, AppVeyor, and Shippable, then compare the generators covered by current tests with those that are not. Done means documenting which additional generator coverage is practical and adding the agreed coverage to the CI configurations.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.