Commit 72ac00d
authored
Adds GIT_AUTHOR_NAME to the test env (#6825)
## What's the problem this PR addresses?
The test env doesn't automatically setup the git committer name / email.
I noticed it when working on `yarn init`, as the test was passing but I
didn't understand why until I dig deeper (turns out we don't pass the
`strict` flag when calling the `git` commands; I don't remember whether
it's an oversight or not).
## How did you fix it?
Automatically setup the git committer name / email. Should a test want
to avoid that (for example to explicitly test that a command works
without), they should override it manually.
## Checklist
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.
<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.1 parent e65f166 commit 72ac00d
File tree
1 file changed
+5
-0
lines changed- packages/acceptance-tests/pkg-tests-core/sources/utils
1 file changed
+5
-0
lines changedLines changed: 5 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
56 | 56 | | |
57 | 57 | | |
58 | 58 | | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
59 | 64 | | |
60 | 65 | | |
61 | 66 | | |
| |||
0 commit comments