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
Copy file name to clipboardExpand all lines: doc/repository-library-onboarding.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ This guide should be followed when onboarding new repositories/libraries.
7
7
2) Add `.librarian` directory to your repository with appropriate configuration files. See details [here](https://github.com/googleapis/librarian/blob/main/doc/language-onboarding.md#configure-repository-to-work-with-librarian-cli)
8
8
3) You should only start with 1 library to validate the flow (follow instructions below)
9
9
4) If your repository contains multiple libraries, start ramping up slowly until all libraries are in your `state.yaml` file and have migrated to librarian.
10
-
5) To complete onboarding you should run the librarian test-container generate command to validate that all libraries are getting generated correctly. Note this command is WIP, [documentation will be added](https://github.com/googleapis/librarian/issues/2621) once available.
10
+
5) To complete onboarding you should run the librarian test-container generate command to validate that all libraries are getting generated correctly. Note this standalone command is WIP, currently you can run [update-image](https://pkg.go.dev/github.com/googleapis/librarian/cmd/librarian#hdr-update_image) command with `-test` flag to trigger tests after generation.
11
11
6) To correctly parse the commit message of a merge commit, only allow squash merging
12
12
and set the default commit message to **Pull request title and description**.
0 commit comments