Skip to content

Commit 3f0c562

Browse files
authored
Merge pull request #56 from themr0c/readme-migration-step-2
2 parents e547b4a + 3d747e1 commit 3f0c562

12 files changed

+165
-64
lines changed

.github/workflows/main.yml

Lines changed: 0 additions & 26 deletions
This file was deleted.

.github/workflows/vale.yml

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
name: Linting with Vale
2+
on: [push]
3+
4+
jobs:
5+
prose:
6+
runs-on: ubuntu-latest
7+
steps:
8+
- name: Checkout
9+
uses: actions/checkout@master
10+
11+
- name: Vale Linter
12+
uses: errata-ai/[email protected]
13+
with:
14+
files: __onlyModified
15+
env:
16+
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.htmltest.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,3 +19,4 @@ ExternalTimeout: 60 # (seconds) default is 15.
1919
IgnoreURLs:
2020
- https://cse.google.com/cse.js
2121
- https://github.com/rolfedh/studious-fortnight
22+
- https://marketplace.visualstudio.com

CONTRIBUTING.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,3 @@
11
# Contributor's guide
22

3+
* See: link:https://rolfedh.github.io/studious-fortnight/docs/end-user-guide/contributing/[Contributing].

README.adoc

Lines changed: 2 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -2,42 +2,10 @@
22

33
This repository helps tech writers at Red Hat get up and running with Vale. It serves as the starting point for the Vale Community of Practice at Red Hat.
44

5-
## Understanding `vale` usage
5+
* See the documentation: link:https://rolfedh.github.io/studious-fortnight/[Vale for Red Hat documentation writers]
66
7-
* See: link:https://rolfedh.github.io/studious-fortnight/docs/end-user-guide/introduction/[]
8-
9-
10-
## Contributing to this project
11-
12-
image::images/open-source-wants-you-39-percent.jpg[Open Source Wants You]
13-
14-
You can help by doing any of the following:
15-
* Use Vale with the style rules from this studious-fortnight repository.
16-
* Report issues and request enhancements.
17-
* Authoring style rules.
18-
19-
To become a contributor, see xref:CONTRIBUTING.adoc[].
20-
21-
22-
## Getting started with vale
23-
24-
* See: link:https://rolfedh.github.io/studious-fortnight/docs/end-user-guide/getting-started-with-vale/[]
25-
26-
27-
## Optional next steps
28-
29-
* link:https://code.visualstudio.com/docs/?dv=linux64_rpm[Install VisualStudio Code] and the link:https://marketplace.visualstudio.com/items?itemName=errata-ai.vale-server[Vale extension for VisualStudio Code].
30-
* link:https://docs.errata.ai/vale/install#using-vale-with-a-continuous-integration-ci-service[Add Vale to your docs continuous integration (CI) service].
31-
* link:https://github.com/errata-ai/vale-action[Add Vale to your GitHub actions].
32-
33-
## Related topics
7+
.Additional resources
348

359
* xref:troubleshooting-common-errors.md[Troubleshooting common errors]
3610
* xref:vale-at-red-hat-blog.md[Blog posts for Studious-Fortnight]
3711
* xref:https://rolfe.blog/category/vale/[Rolfe's "Vale notes" blog posts]
38-
39-
## How to get involved, get help, and contribute
40-
41-
* Join the Slack channel, link:https://coreos.slack.com/archives/C0218RXJK5E[#vale-at-red-hat], in the CoreOS workspace.
42-
* To report a bug _in this repository_ or request an enhancement, link:https://github.com/rolfedh/studious-fortnight/issues[create an issue].
43-
* To show appreciation and support for Joseph Kato's work on Vale, consider link:https://docs.errata.ai/vale/about#sponsors[making a donation].

modules/end-user-guide/nav.adoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
* xref:introduction.adoc[]
22
* xref:getting-started-with-vale.adoc[]
3-
** xref:understanding-vale-output.adoc[]
4-
** xref:adding-vale-configuration-to-a-project.adoc[]
3+
* xref:understanding-vale-output.adoc[]
4+
* xref::using-vale-in-the-ide.adoc[]
55
* xref:defining-a-vale-onboarding-strategy.adoc[]
6+
* xref:adding-vale-configuration-to-a-project.adoc[]
7+
* xref:using-vale-with-a-continuous-integration-service.adoc[]
68
* xref:contributing.adoc[]
79
** xref:extending-the-vocabulary.adoc[]
810
** xref:extending-styles.adoc[]

modules/end-user-guide/pages/understanding-vale-output.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
// Metadata for Antora
2-
:navtitle: Understanding output
2+
:navtitle: Understanding Vale alerts
33
:keywords: understanding, output
44
// :page-aliases:
55
// End of metadata for Antor
@@ -13,6 +13,6 @@
1313
:context: understanding-vale-output
1414

1515

16-
include::partial$con_understanding-vale-output.adoc[leveloffest=+1]
16+
include::partial$con_understanding-vale-output.adoc[leveloffset=+1]
1717

1818
:context: {parent-context-of-understanding-vale-output}
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
// Metadata for Antora
2+
:navtitle: Vale in the IDE
3+
:keywords: vale
4+
// :page-aliases:
5+
// End of metadata for Antora
6+
7+
:parent-context-of-using-vale-in-the-ide: {context}
8+
9+
[id="using-vale-in-the-ide_{context}"]
10+
= Using vale in the IDE
11+
12+
:context: using-vale-in-the-ide
13+
14+
include::partial$proc_using-vale-in-the-ide.adoc[leveloffset=+1]
15+
16+
17+
:context: {parent-context-of-using-vale-in-the-ide}
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
// Metadata for Antora
2+
:navtitle: Continuous integration
3+
:keywords: vale
4+
// :page-aliases:
5+
// End of metadata for Antora
6+
7+
:parent-context-of-using-vale-with-a-continuous-integration-service: {context}
8+
9+
[id="using-vale-with-a-continuous-integration-service_{context}"]
10+
= Using vale with a continuous integration service
11+
12+
:context: using-vale-with-a-continuous-integration-service
13+
14+
include::partial$proc_using-vale-github-action.adoc[leveloffset=+1]
15+
16+
include::partial$proc_using-vale-with-a-continuous-integration-service.adoc[leveloffset=+1]
17+
18+
19+
:context: {parent-context-of-using-vale-with-a-continuous-integration-service}
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
:_module-type: PROCEDURE
2+
3+
[id="proc_using-vale-github-action_{context}"]
4+
= Using vale GitHub Action
5+
6+
Consider using vale GitHub Action when your repository is hosted on GitHub, to measure or enforce the project compliance with the Style Guides.
7+
8+
.Prerequisites
9+
10+
* xref:getting-started-with-vale.adoc[]
11+
* xref:adding-vale-configuration-to-a-project.adoc[]
12+
* xref:defining-a-vale-onboarding-strategy.adoc[]
13+
14+
.Procedure
15+
16+
* Add a `.github/workflows/vale.yml` file to your repository with following content:
17+
+
18+
[source,yaml]
19+
----
20+
name: Linting with Vale
21+
on: [push]
22+
23+
jobs:
24+
prose:
25+
runs-on: ubuntu-latest
26+
steps:
27+
- name: Checkout
28+
uses: actions/checkout@master
29+
30+
- name: Vale Linter
31+
uses: errata-ai/[email protected]
32+
with:
33+
files: __onlyModified
34+
env:
35+
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
36+
----
37+
38+
.Additional resources
39+
40+
* link:https://github.com/errata-ai/vale-action[Vale GitHub action].

0 commit comments

Comments
 (0)