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.

Sign up for GitHub

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

Jump to bottom

Update README.md #262

Closed
wants to merge 1 commit into from
Closed

Update README.md #262

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,19 +82,19 @@ More info on how to specify what files to sync where [below](#%EF%B8%8F-sync-con

### Versioning

To always use the latest version of the action add the `latest` tag to the action name like this:
To always use the latest version of the action add the `master` tag to the action name like this:

```yml
uses: BetaHuhn/repo-file-sync-action@latest
uses: BetaHuhn/repo-file-sync-action@master
```

If you want to make sure that your workflow doesn't suddenly break when a new major version is released, use the `v1` tag instead (recommended usage):
If you want to make sure that your workflow doesn't suddenly break when a new major version is released, use a specific version `v1` tag instead (recommended usage):

```yml
uses: BetaHuhn/repo-file-sync-action@v1
```

With the `v1` tag you will always get the latest non-breaking version which will include potential bug fixes in the future. If you use a specific version, make sure to regularly check if a new version is available, or enable Dependabot.
If you use a specific version, make sure to regularly check if a new version is available, or enable Dependabot.

## ⚙️ Action Inputs

Expand Down