chore: add librarian state.yaml #14108
Conversation
parthea
changed the title
|
|
parthea
added
the
owlbot:run
gcf-owl-bot
bot
removed
the
owlbot:run
| remove_regex: '' | ||
| sourcePaths: | ||
| - packages/google-cloud-language | ||
| version: 2.17.2 |
There was a problem hiding this comment.
Can you file and link an issue here to remove this file once we're done with our local testing?
There was a problem hiding this comment.
We won't be deleting state.yaml. The plan is to have an initial state.yaml when we onboard
There was a problem hiding this comment.
I think Librarian will be creating the state.yaml file and maintaining it once we have configure implemented. Ideally, state.yaml shouldn't have any manual edits.
We're only creating this file for the first milestone. Once we've got configure in place, Librarian should create and place the state.yaml file in the /.librarian folder.
Why do we want an initial handwritten state.yaml (apart from the first milestone)?
There was a problem hiding this comment.
I think Librarian will be creating the state.yaml file
Let's sync offline on this. My initial thought is that we will create the initial state.yaml, and update it as needed, and Librarian will fully take over state.yaml only once we've completed the migration from owlbot->librarian.
parthea
added
the
owlbot:run
gcf-owl-bot
bot
removed
the
owlbot:run
| remove_regex: '' | ||
| sourcePaths: | ||
| - packages/google-cloud-language | ||
| version: 2.17.2 |
There was a problem hiding this comment.
I think Librarian will be creating the state.yaml file and maintaining it once we have configure implemented. Ideally, state.yaml shouldn't have any manual edits.
We're only creating this file for the first milestone. Once we've got configure in place, Librarian should create and place the state.yaml file in the /.librarian folder.
Why do we want an initial handwritten state.yaml (apart from the first milestone)?
2 participants
Fixes googleapis/librarian#867