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

Adds "commented" website front matter to docs #500

Merged
merged 3 commits into from
Mar 26, 2020
Merged

Adds "commented" website front matter to docs #500

merged 3 commits into from
Mar 26, 2020

Conversation

skaegi
Copy link
Contributor

@skaegi skaegi commented Mar 25, 2020

This change adds the front matter needed for the website without altering the site markdown or adding titles. It does this by adding the front matter in comment tags.

The tutorial and install are not part of the website currently so links to them under docs/ use absolute urls to allow them to work in both the website and in the pipeline repo

Changes

update /docs markdown files with front matter

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

This change adds the front matter needed for the website without altering the site markdown or adding titles. It does this by adding the front matter in comment tags.

The tutorial and install are not part of the website currently so links to them under docs/ use absolute urls to allow them to work in both the website and in the pipeline repo
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 25, 2020
@skaegi
Copy link
Contributor Author

skaegi commented Mar 25, 2020

/retest

docs/README.md Outdated
@@ -19,5 +28,5 @@ See the following links for more on each of the resources involved:

## Getting Started Tasks

- [Create an Ingress on the EventListener Service](create-ingress.yaml)
- [Create a GitHub webhook](create-webhook.yaml)
- [Create an Ingress on the EventListener Service](https://github.com/tektoncd/triggers/blob/master/docs/create-ingress.yaml)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having the branch hard coded here would break links to any new versioned docs that we have here: https://github.com/tektoncd/triggers#read-the-docs

Do we need to keep the absolute urls forever or can that be changed back when its part of the website?

Copy link
Contributor Author

@skaegi skaegi Mar 25, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely short term.
Let me see if I can workaround that as everything under docs should come as a unit. The "sync" done by the website is currently very simple and does not pick-up files that are not markdown.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One option is to leave it as a broken link in the website until we can figure out the right thing to do. I have no problem err-ing on the side of keeping our current github doc pristine.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool, let's keep the relative links for now then.

For now we'll continue to use relative links for non-markdown resources which will make our links broken in the website however we will fix this later.

I have left the "image" as an absolute URL (short-term) as I feel that is essential for the docs and hopefully will not change in the short-term.
@dibyom
Copy link
Member

dibyom commented Mar 25, 2020

I0325 15:52:21.743] pkg/apis/triggers/v1alpha1/event_listener_validation.go:65:31: S1039: unnecessary use of fmt.Sprintf (gosimple)
I0325 15:52:21.747] return apis.ErrMissingField(fmt.Sprintf("template.name"))

Not sure why the linter is failing for this in this PR 🤔

@skaegi
Copy link
Contributor Author

skaegi commented Mar 25, 2020

well... why not try another...
/retest

@dibyom
Copy link
Member

dibyom commented Mar 25, 2020

@skaegi I'll look into the linter issue....to unblock this PR would you mind making the lint change..it should be simple...
pkg/apis/triggers/v1alpha1/event_listener_validation.go:65:31
return apis.ErrMissingField(fmt.Sprintf("template.name")) to
return apis.ErrMissingField("template.name")

@dibyom
Copy link
Member

dibyom commented Mar 26, 2020

/lgtm
/approve

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2020
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 26, 2020
@tekton-robot tekton-robot merged commit a0fd950 into tektoncd:master Mar 26, 2020
@ncskier ncskier mentioned this pull request Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants