@@ -29,7 +29,8 @@ for contributing to the project.
2929### Forking the isce3 repository
3030
3131If you are a first-time contributor, the first thing you should do is fork the
32- isce3 repository to create your own copy of the project.
32+ isce3 repository to create your own copy of the project. (External contributors
33+ cannot directly create or modify branches on the isce3 repository.)
3334
34351 . Go to https://github.com/isce-framework/isce3 and click on the "Fork"
3536 button.
@@ -161,11 +162,22 @@ quality of the project.
161162
162163- Review may be requested by a PR author and/or other team members. Reviewers
163164 can make comments, request changes, or approve the PR, indicating that it has
164- been carefully examined and is ready for merging. Before a PR can be merged,
165- it must be approved by at least two core team members.
165+ been carefully examined and is ready for merging.
166+ - Before a PR can be merged, it must be approved by at least two core team
167+ members.
168+
169+ # ## Testing and scanning
170+
166171- CI jobs that build and test the code are automatically triggered upon each PR
167172 update. The CI tests must pass before your PR can be merged. To avoid overuse
168173 of these resources, it' s helpful to test all changes locally before committing
169174 and push commits in batches rather than individually.
170- - After all required checks have passed, the PR can be merged by pressing the
171- "Squash and merge" button.
175+ - Each commit is scanned using
176+ [detect-secrets](https://github.com/Yelp/detect-secrets) and
177+ [CodeQL](https://codeql.github.com/) to identify possible security
178+ vulnerabilities and exposed credentials. Commits containing either may be
179+ blocked.
180+ - Linters may be run on the changes and may reject PRs that don' t conform to the
181+ project' s style conventions.
182+
183+ After all required checks have passed, the PR may be merged by a maintainer.
0 commit comments