Compare commits

...

3 Commits

Author SHA1 Message Date
cjc7373 2eb7fbaab9
Merge 96e67d5384 into 44c2b7a8a4 2024-05-02 17:54:06 +02:00
Cory Miller 44c2b7a8a4
README: Suggest `user.email` to be `41898282+github-actions[bot]@users.noreply.github.com` (#1707)
* README: Set `user.email` to GitHub Actions Bot

* Update workflow to use proper bot GitHub Bot email

* Prefix `user.email` with `41898282+`

To match squash merge user, else showing as two different users, see: b0948d0da0

* Update README.md

---------

Co-authored-by: Pelle Wessman <pelle@kodfabrik.se>
2024-04-30 11:50:54 -04:00
cjc7373 96e67d5384
doc: clarify the behavior of a pull_request event 2024-02-27 18:03:06 +08:00
2 changed files with 7 additions and 4 deletions

View File

@ -27,8 +27,8 @@ jobs:
fetch-depth: 0
- name: Git config
run: |
git config user.name github-actions
git config user.email github-actions@github.com
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
- name: Tag new target
run: git tag -f ${{ github.event.inputs.major_version }} ${{ github.event.inputs.target }}
- name: Push new tag

View File

@ -248,6 +248,8 @@ Please refer to the [release page](https://github.com/actions/checkout/releases/
## Checkout pull request HEAD commit instead of merge commit
The default behavior of a `pull_request` event is to checkout to a ref that already merged your branch into the base branch (So don't be surprised to see the SHA checked out doesn't match your local HEAD SHA). You can change that to checkout your pull request's HEAD by:
```yaml
- uses: actions/checkout@v4
with:
@ -279,8 +281,9 @@ jobs:
- uses: actions/checkout@v4
- run: |
date > generated.txt
git config user.name github-actions
git config user.email github-actions@github.com
# Note: the following account information will not work on GHES
git config user.name "github-actions[bot]"
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
git add .
git commit -m "generated"
git push