Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Task for running linting (markdownlint, …) #558

Closed
vdemeester opened this issue Feb 27, 2019 · 0 comments · Fixed by #954 or tektoncd/catalog#43
Closed

Create Task for running linting (markdownlint, …) #558

vdemeester opened this issue Feb 27, 2019 · 0 comments · Fixed by #954 or tektoncd/catalog#43
Assignees
Labels
area/yamls This issue involves writing a lot of yaml

Comments

@vdemeester
Copy link
Member

vdemeester commented Feb 27, 2019

Expected Behavior

We should be testing and releasing Pipelines with Pipelines.

We should have a Task (and related Resources) defined that we can use to:

  • Run our "linting" (markdownlint, …)

The Task

  • Inputs:
    • git repo
  • Outputs:
  • Parameters:
    • some kind of gubernator endpoint info, will have to look into existing scripts to figure this out

Actual Behavior

We currently use prow.

This is where the current markdown linting is implemented: markdown_build_tests

Note that these both only are applied to markdown files that have changed - we can leave that out of scope for this issue and apply the linting to all markdown files each run.

Additional Info

  • Actually triggering this is not in scope for this issue, it's fine to test manually (we'll be linking these together in a later issue)

/cc @bobcatfish

@bobcatfish bobcatfish added the area/yamls This issue involves writing a lot of yaml label Feb 28, 2019
@bobcatfish bobcatfish added this to the Pipelines 0.5 🐱 milestone May 28, 2019
@vdemeester vdemeester self-assigned this May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/yamls This issue involves writing a lot of yaml
Projects
None yet
2 participants