Add instructions on how to user a different user (#140)
* Add instructions on how to user a different user * Fix wording * Use special GitHub-provided mail for push examples * Apply suggestions from code review Co-authored-by: Federico Grandi <fgrandi30@gmail.com>
This commit is contained in:
15
README.md
15
README.md
@@ -104,6 +104,21 @@ For more info on how to use outputs, see ["Context and expression syntax"](https
|
||||
|
||||
### Examples:
|
||||
|
||||
If you don't want to use your GitHub username for the CI commits, you can [also use the user provided by GitHub for this task](https://github.com/actions/checkout/#push-a-commit-using-the-built-in-token):
|
||||
```yaml
|
||||
on: push
|
||||
jobs:
|
||||
build:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: EndBug/add-and-commit@v7.0.0
|
||||
with:
|
||||
author_name: github-actions
|
||||
author_email: 41898282+github-actions[bot]@users.noreply.github.com
|
||||
```
|
||||
|
||||
`41898282+github-actions[bot]@users.noreply.github.com` is the mail of the original GitHub Actions bot. If you use that, [the GitHub avatar is shown for the commits](https://github.community/t/github-actions-bot-email-address/17204).
|
||||
|
||||
Do you want to lint your JavaScript files, located in the `src` folder, with ESLint, so that fixable changes are done without your intervention? You can use a workflow like this:
|
||||
|
||||
```yaml
|
||||
|
||||
Reference in New Issue
Block a user