You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start by filing an issue. The existing committers on this project work to reach
16
+
consensus around project direction and issue solutions within issue threads
17
+
(when appropriate).
18
+
19
+
## Contributor License Agreement
20
+
21
+
All third-party contributions to this project must be accompanied by a signed contributor
22
+
license agreement. This gives Adobe permission to redistribute your contributions
23
+
as part of the project. [Sign our CLA](https://opensource.adobe.com/cla.html). You
24
+
only need to submit an Adobe CLA one time, so if you have submitted one previously,
25
+
you are good to go!
26
+
27
+
## Code Reviews
28
+
29
+
All submissions should come in the form of pull requests and need to be reviewed
30
+
by project committers. Read [GitHub's pull request documentation](https://help.github.com/articles/about-pull-requests/)
31
+
for more information on sending pull requests.
32
+
33
+
Lastly, please follow the [pull request template](PULL_REQUEST_TEMPLATE.md) when
34
+
submitting a pull request!
35
+
36
+
## From Contributor To Committer
37
+
38
+
We love contributions from our community! If you'd like to go a step beyond contributor
39
+
and become a committer with full write access and a say in the project, you must
40
+
be invited to the project. The existing committers employ an internal nomination
41
+
process that must reach lazy consensus (silence is approval) before invitations
42
+
are issued. If you feel you are qualified and want to get more deeply involved,
43
+
feel free to reach out to existing committers to have a conversation about that.
44
+
45
+
## Security Issues
46
+
47
+
Security issues shouldn't be reported on this issue tracker. Instead, [file an issue to our security experts](https://helpx.adobe.com/security/alertus.html).
<!--- STOP! Before you open an issue please search this repository's issues to see if it has already been reported. This helps reduce duplicate issues from being created. -->
2
+
<!--- SECURITY DISCLOSURE: If this is a security disclosure please follow the guidelines in CONTRIBUTING.md. This helps keep folks from accidentally releasing vulnerabilities before the maintainers get a chance to fix the issue. -->
3
+
4
+
### Expected Behaviour
5
+
6
+
### Actual Behaviour
7
+
8
+
### Reproduce Scenario (including but not limited to)
uses: actions/[email protected]# If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
uses: actions/[email protected]# If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
uses: actions/[email protected]# If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
uses: actions/[email protected]# If you're using actions/checkout@v2 you must set persist-credentials to false in most cases for the deployment to work correctly.
11
+
with:
12
+
persist-credentials: false
13
+
- name: NPM Install
14
+
uses: bahmutov/npm-install@v1
15
+
- name: Build
16
+
run: |
17
+
npm run build
18
+
env:
19
+
PREFIX_PATHS: true # equivalent to --prefix-paths flag for 'gatsby build'
0 commit comments