Test GitHub Super Linter for development

Open
#1,044 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd, tooling

Research direction

Start with the linked GitHub Super Linter announcement and inspect the repository's existing Travis CI and AppVeyor setup. Test whether Super Linter improves feedback time, then document the setup requirements and comparison results so the project can decide whether to adopt it.

Written by the indexing model from the issue text.

Description

Needs Testing

Play with the new GitHub Super Linter to see if it saves time over waiting for fail reports from Travis CI and AppVeyor.

Dominant language
Python
Stars
123
Forks
20
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 WheatonCS/Lexos

All issues in WheatonCS/Lexos

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.