Skip to content

Commit e43997a

Browse files
committed
Fixing super linter issues
1 parent 6c0bf85 commit e43997a

File tree

4 files changed

+383
-171
lines changed

4 files changed

+383
-171
lines changed

README.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
1+
<!-- markdownlint-disable -->
2+
13
<p align="center">
24
<a href="https://github.com/geoadmin/action-milestone-tag/actions">
35
<img alt="action-milestone-tag status" src="https://github.com/geoadmin/action-milestone-tag/workflows/build-test/badge.svg">
46
</a>
57
</p>
68

7-
# Create a git tag based on the attached milestone
9+
# Create a Git tag based on the attached milestone
810

911
- [Description](#description)
1012
- [Inputs](#inputs)
@@ -18,7 +20,7 @@
1820

1921
## Description
2022

21-
This github action can be used on pull request merge to tag the repository. The
23+
This Github action can be used on pull request merge to tag the repository. The
2224
tag name is based on the attached milestone if any or on the previous tag.
2325

2426
You can also use the input `custom_tag` to modify the tag name by for example
@@ -110,7 +112,7 @@ Make sure your changes follows the formatting and linting
110112
npm run format-check && npm run lint
111113
```
112114

113-
Build the typescript and package it for distribution
115+
Build the Typescript and package it for distribution
114116

115117
```bash
116118
npm run build && npm run package
@@ -131,7 +133,7 @@ $ npm test
131133

132134
### Create new Release
133135

134-
Actions are run from GitHub repos so we will checkin the packed dist folder.
136+
Actions are run from GitHub repos so we will checking the packed dist folder.
135137

136138
1. First make sure the version in `package.json` match the next release version,
137139
if not update it.
@@ -150,8 +152,8 @@ Actions are run from GitHub repos so we will checkin the packed dist folder.
150152

151153
### Validate
152154

153-
You can now validate the action by referencing `./` in a workflow in your repo
154-
(see [test.yml](.github/workflows/test.yml))
155+
You can now validate the action by referencing `./` in a workflow in your
156+
repository (see [test.yml](.github/workflows/test.yml))
155157

156158
```yaml
157159
uses: ./

0 commit comments

Comments
 (0)