Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Latest commit

 

History

History
History
28 lines (19 loc) · 1.3 KB

File metadata and controls

28 lines (19 loc) · 1.3 KB
Copy raw file
Download raw file
Outline
Edit and raw actions

Submodules

While most developers will not have to deal with submodules on a regular basis, those who do should read this information. The submodules currently in this project are:

  • src/Modules/Pester: The Pester testing framework for PowerShell

  • src/libpsl-native/test/googletest: The GoogleTest framework for Linux native code

Rebase and Fast-Forward Merge Pull Requests in Submodules

This is not necessary in the superproject, only submodules!

DO NOT commit updates unless absolutely necessary. When submodules must be updated, a separate Pull Request must be submitted, reviewed, and merged before updating the superproject.

Because GitHub's "Merge Pull Request" button merges with --no-ff, an extra merge commit will always be created. This is especially annoying when trying to commit updates to submodules. Therefore our policy is to merge using the Git CLI after approval, with a rebase onto master to enable a fast-forward merge.

When committing submodule updates, ensure no other changes are in the same commit. Submodule bumps may be included in feature branches for ease of work, but the update must be independently approved before merging into master.

Morty Proxy This is a proxified and sanitized view of the page, visit original site.