Skip to content

Commit bca5d34

Browse files
docs: updated code of conduct/build files (#1329)
* build: only check --engine-strict for production deps Co-authored-by: Justin Beckwith <[email protected]> Source-Author: Benjamin E. Coe <[email protected]> Source-Date: Thu Oct 15 17:40:52 2020 -0700 Source-Repo: googleapis/synthtool Source-Sha: 5451633881133e5573cc271a18e73b18caca8b1b Source-Link: googleapis/synthtool@5451633 * chore: clean up Node.js TOC for cloud-rad Source-Author: F. Hinkelmann <[email protected]> Source-Date: Wed Oct 21 09:26:04 2020 -0400 Source-Repo: googleapis/synthtool Source-Sha: f96d3b455fe27c3dc7bc37c3c9cd27b1c6d269c8 Source-Link: googleapis/synthtool@f96d3b4 * chore: fix Node.js TOC for cloud-rad Source-Author: F. Hinkelmann <[email protected]> Source-Date: Wed Oct 21 12:01:24 2020 -0400 Source-Repo: googleapis/synthtool Source-Sha: 901ddd44e9ef7887ee681b9183bbdea99437fdcc Source-Link: googleapis/synthtool@901ddd4 * chore(docs): update code of conduct of synthtool and templates Source-Author: Christopher Wilcox <[email protected]> Source-Date: Thu Oct 22 14:22:01 2020 -0700 Source-Repo: googleapis/synthtool Source-Sha: 5f6ef0ec5501d33c4667885b37a7685a30d41a76 Source-Link: googleapis/synthtool@5f6ef0e * build(node): update testing matrix Source-Author: Benjamin E. Coe <[email protected]> Source-Date: Thu Oct 22 22:32:52 2020 -0500 Source-Repo: googleapis/synthtool Source-Sha: b7413d38b763827c72c0360f0a3d286c84656eeb Source-Link: googleapis/synthtool@b7413d3 * build(node): don't run prepare during smoke test Source-Author: Benjamin E. Coe <[email protected]> Source-Date: Fri Oct 23 17:27:51 2020 -0400 Source-Repo: googleapis/synthtool Source-Sha: a783321fd55f010709294455584a553f4b24b944 Source-Link: googleapis/synthtool@a783321 * build(node): cleanup production deps before installing dev/production Source-Author: Benjamin E. Coe <[email protected]> Source-Date: Mon Oct 26 10:37:03 2020 -0400 Source-Repo: googleapis/synthtool Source-Sha: 89c849ba5013e45e8fb688b138f33c2ec6083dc5 Source-Link: googleapis/synthtool@89c849b
1 parent f9b16d8 commit bca5d34

File tree

4 files changed

+104
-43
lines changed

4 files changed

+104
-43
lines changed

Diff for: .github/workflows/ci.yaml

+11-5
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,20 @@ jobs:
99
runs-on: ubuntu-latest
1010
strategy:
1111
matrix:
12-
node: [10, 12, 13]
12+
node: [10, 12, 14, 15]
1313
steps:
1414
- uses: actions/checkout@v2
1515
- uses: actions/setup-node@v1
1616
with:
1717
node-version: ${{ matrix.node }}
1818
- run: node --version
19-
- run: npm install --engine-strict
19+
# The first installation step ensures that all of our production
20+
# dependencies work on the given Node.js version, this helps us find
21+
# dependencies that don't match our engines field:
22+
- run: npm install --production --engine-strict --ignore-scripts --no-package-lock
23+
# Clean up the production install, before installing dev/production:
24+
- run: rm -rf node_modules
25+
- run: npm install
2026
- run: npm test
2127
- name: coverage
2228
uses: codecov/codecov-action@v1
@@ -29,7 +35,7 @@ jobs:
2935
- uses: actions/checkout@v2
3036
- uses: actions/setup-node@v1
3137
with:
32-
node-version: 12
38+
node-version: 14
3339
- run: npm install
3440
- run: npm test
3541
- name: coverage
@@ -43,7 +49,7 @@ jobs:
4349
- uses: actions/checkout@v2
4450
- uses: actions/setup-node@v1
4551
with:
46-
node-version: 12
52+
node-version: 14
4753
- run: npm install
4854
- run: npm run lint
4955
docs:
@@ -52,6 +58,6 @@ jobs:
5258
- uses: actions/checkout@v2
5359
- uses: actions/setup-node@v1
5460
with:
55-
node-version: 12
61+
node-version: 14
5662
- run: npm install
5763
- run: npm run docs-test

Diff for: .kokoro/release/docs-devsite.sh

+4
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Diff for: CODE_OF_CONDUCT.md

+87-36
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,94 @@
1-
# Contributor Code of Conduct
1+
<!-- # Generated by synthtool. DO NOT EDIT! !-->
2+
# Code of Conduct
23

3-
As contributors and maintainers of this project,
4-
and in the interest of fostering an open and welcoming community,
5-
we pledge to respect all people who contribute through reporting issues,
6-
posting feature requests, updating documentation,
7-
submitting pull requests or patches, and other activities.
4+
## Our Pledge
85

9-
We are committed to making participation in this project
10-
a harassment-free experience for everyone,
11-
regardless of level of experience, gender, gender identity and expression,
12-
sexual orientation, disability, personal appearance,
13-
body size, race, ethnicity, age, religion, or nationality.
6+
In the interest of fostering an open and welcoming environment, we as
7+
contributors and maintainers pledge to making participation in our project and
8+
our community a harassment-free experience for everyone, regardless of age, body
9+
size, disability, ethnicity, gender identity and expression, level of
10+
experience, education, socio-economic status, nationality, personal appearance,
11+
race, religion, or sexual identity and orientation.
12+
13+
## Our Standards
14+
15+
Examples of behavior that contributes to creating a positive environment
16+
include:
17+
18+
* Using welcoming and inclusive language
19+
* Being respectful of differing viewpoints and experiences
20+
* Gracefully accepting constructive criticism
21+
* Focusing on what is best for the community
22+
* Showing empathy towards other community members
1423

1524
Examples of unacceptable behavior by participants include:
1625

17-
* The use of sexualized language or imagery
18-
* Personal attacks
19-
* Trolling or insulting/derogatory comments
20-
* Public or private harassment
21-
* Publishing other's private information,
22-
such as physical or electronic
23-
addresses, without explicit permission
24-
* Other unethical or unprofessional conduct.
26+
* The use of sexualized language or imagery and unwelcome sexual attention or
27+
advances
28+
* Trolling, insulting/derogatory comments, and personal or political attacks
29+
* Public or private harassment
30+
* Publishing others' private information, such as a physical or electronic
31+
address, without explicit permission
32+
* Other conduct which could reasonably be considered inappropriate in a
33+
professional setting
34+
35+
## Our Responsibilities
36+
37+
Project maintainers are responsible for clarifying the standards of acceptable
38+
behavior and are expected to take appropriate and fair corrective action in
39+
response to any instances of unacceptable behavior.
2540

2641
Project maintainers have the right and responsibility to remove, edit, or reject
27-
comments, commits, code, wiki edits, issues, and other contributions
28-
that are not aligned to this Code of Conduct.
29-
By adopting this Code of Conduct,
30-
project maintainers commit themselves to fairly and consistently
31-
applying these principles to every aspect of managing this project.
32-
Project maintainers who do not follow or enforce the Code of Conduct
33-
may be permanently removed from the project team.
34-
35-
This code of conduct applies both within project spaces and in public spaces
36-
when an individual is representing the project or its community.
37-
38-
Instances of abusive, harassing, or otherwise unacceptable behavior
39-
may be reported by opening an issue
40-
or contacting one or more of the project maintainers.
41-
42-
This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.2.0,
43-
available at [http://contributor-covenant.org/version/1/2/0/](http://contributor-covenant.org/version/1/2/0/)
42+
comments, commits, code, wiki edits, issues, and other contributions that are
43+
not aligned to this Code of Conduct, or to ban temporarily or permanently any
44+
contributor for other behaviors that they deem inappropriate, threatening,
45+
offensive, or harmful.
46+
47+
## Scope
48+
49+
This Code of Conduct applies both within project spaces and in public spaces
50+
when an individual is representing the project or its community. Examples of
51+
representing a project or community include using an official project e-mail
52+
address, posting via an official social media account, or acting as an appointed
53+
representative at an online or offline event. Representation of a project may be
54+
further defined and clarified by project maintainers.
55+
56+
This Code of Conduct also applies outside the project spaces when the Project
57+
Steward has a reasonable belief that an individual's behavior may have a
58+
negative impact on the project or its community.
59+
60+
## Conflict Resolution
61+
62+
We do not believe that all conflict is bad; healthy debate and disagreement
63+
often yield positive results. However, it is never okay to be disrespectful or
64+
to engage in behavior that violates the project’s code of conduct.
65+
66+
If you see someone violating the code of conduct, you are encouraged to address
67+
the behavior directly with those involved. Many issues can be resolved quickly
68+
and easily, and this gives people more control over the outcome of their
69+
dispute. If you are unable to resolve the matter for any reason, or if the
70+
behavior is threatening or harassing, report it. We are dedicated to providing
71+
an environment where participants feel welcome and safe.
72+
73+
Reports should be directed to *[email protected]*, the
74+
Project Steward(s) for *Google Cloud Client Libraries*. It is the Project Steward’s duty to
75+
receive and address reported violations of the code of conduct. They will then
76+
work with a committee consisting of representatives from the Open Source
77+
Programs Office and the Google Open Source Strategy team. If for any reason you
78+
are uncomfortable reaching out to the Project Steward, please email
79+
80+
81+
We will investigate every complaint, but you may not receive a direct response.
82+
We will use our discretion in determining when and how to follow up on reported
83+
incidents, which may range from not taking action to permanent expulsion from
84+
the project and project-sponsored spaces. We will notify the accused of the
85+
report and provide them an opportunity to discuss it before any action is taken.
86+
The identity of the reporter will be omitted from the details of the report
87+
supplied to the accused. In potentially harmful situations, such as ongoing
88+
harassment or threats to anyone's safety, we may take action without notice.
89+
90+
## Attribution
91+
92+
This Code of Conduct is adapted from the Contributor Covenant, version 1.4,
93+
available at
94+
https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

Diff for: synth.metadata

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@
44
"git": {
55
"name": ".",
66
"remote": "https://github.com/googleapis/nodejs-storage.git",
7-
"sha": "c77eaa363be18b6b9ddd1f7b505e23be8cd5bf98"
7+
"sha": "f9b16d82e5c6a26d76f721a277cf07b518b63a42"
88
}
99
},
1010
{
1111
"git": {
1212
"name": "synthtool",
1313
"remote": "https://github.com/googleapis/synthtool.git",
14-
"sha": "0c868d49b8e05bc1f299bc773df9eb4ef9ed96e9"
14+
"sha": "89c849ba5013e45e8fb688b138f33c2ec6083dc5"
1515
}
1616
}
1717
],

0 commit comments

Comments
 (0)