Closed jacyang2010 closed 1 year ago
LGTM Can you put some text around the issue that occurred and some test results after the fix
We can then merge it
The procedure for PRs for canada-ca is to get 1+ approval reviews and then update the title with something like "ready to merge" - see PRs already committed -timeline is 2 to 14 days, use your fork repo for dev work until the pr is in
Code change reviewed OK
LGTM
LGTM Can you put some text around the issue that occurred and some test results after the fix
We can then merge it
The procedure for PRs for canada-ca is to get 1+ approval reviews and then update the title with something like "ready to merge" - see PRs already committed -timeline is 2 to 14 days, use your fork repo for dev work until the pr is in
OK
I have no permission to invite people to review this PR. @fmichaelobrien
The pbmm and pubsec repos are under the google org so access can be granted and invites to the PR can be assigned there normally. None of us are part of this CA repo so PR reviews are done adhoc by pasting a note to this PR of something like "approved".
If it is made clear through comments that 1+ other GitHub users from google traditionally and now from your org - approve the pr and optionally view or run the patch. We are good.
The org owner will merge the pr then
As it stands there is one approving review
Code change reviewed OK
LGTM
I will treat this message as an approval varient even though the expected keyword "approved" is not mentioned. Please let me know if I was wrong. @fmichaelobrien
Yes on the pubsec repo we usually sign an approval with LGTM
Example https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/317
For this pr
LGTM Approved Ready to merge
@ptd-tbs and team PR was reviewed and PR is ready to merge
@ptd-tbs the PR is ready to merge @jacyang2010 for the time being - you can fork the repo with the PR change and use the fork until this upstream is merged Use the existing fork that is the pr source below https://github.com/yw-liftandshift/cloud-guardrails-gcp from https://github.com/canada-ca/cloud-guardrails-gcp/forks
@fmichaelobrien we are actually not blocked by this PR and we have patched the clone of this repo before pushing it to the guardrails CSR of the landing zone deployment instance. Thanks for your reminder anyways.
Sounds good, I was pinged by management about a blocker here yesterday.
Thank you @ptd-tbs for the merge - appreciated
This PR should resolve the following issues: #13
Changes:
Test Result:
Please see the test result evidence from the cloud build logs below.